-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(bundler): display name for bundle #9175
feat(bundler): display name for bundle #9175
Conversation
6525d46
to
d9d658d
Compare
Hi, thanks for contributing! This is not a full review yet, as i don't have time today to actually try it out but for a start 2 remarks:
|
@FabianLars Hi! Thanks for the quick comment.
|
d9d658d
to
6d86ff5
Compare
Done updating the change. Please let me know if there are anything missing :) |
bbbff88
to
23d9604
Compare
Hi @FabianLars, is it possible to include this change in 2.0 release? |
23d9604
to
cf7dfc8
Compare
I hope so, yes. I didn't try it yet but your changes look correct and reasonable as far as i can see. Paging @amrbashir for a double check on the windows installers |
Is it easy to confuse "product name" and "display name"? |
@xuchaoqian Sounds good too, especially for Linux |
I am not keen on adding another option that is almost identical to #8109 can be fixed by keeping the executable name generated from cargo and avoid renaming it. #8349 can be fixed by removing the implicit kebab-case conversion and ensure that #8363 can be fixed by modifying the codepage and/or using a Chinese locale. |
sounds good to me too ig 🤷 |
cc @lucasfernog |
I like @amrbashir idea. But we need to at least make a copy of the binary to change its name, otherwise it'll look weird on linux and windows. If we're going to break the bundler output paths, please do so asap. |
Could you explain a bit more, not sure if I understand the issue |
@amrbashir Thanks for your input, and I have some ideas about the solutions you've mentioned.
This sound great, will you make bundler respect binary name defined in
I'm afraid this will have some issues, because debian package names are having lower-kebab-case. If you override |
Feel free to open a PR. The CLI renames the binary after it gets generated by Cargo, we just need to remove that behavior.
Not sure I quite follow what you mean, but we only need to use kebab-case where required and keep everything else as the normal non-kebab-case productName. |
For bundles like For example, when the product name is Can this case be covered? |
I believe that could be covered by using a custom |
Exactly |
I solved it by doing this:
Not very straightforward but works fine |
Oh, awesome! Do you know if that works on Tauri v1 as well (otherwise I can just https://tryitands.ee)? Edit: it seems to work! I had to surround |
Just a note that we have decided to add |
This PR Is for #8109, #8349 and #8363.
For Linux, productName needs to be converted to lower-kebab-case. To make sure app desktop entry displays user friendly name,
displayName
has been added.Example: