-
-
Notifications
You must be signed in to change notification settings - Fork 9
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: added optional short_app_name web config (#54) #55
Conversation
@OutdatedGuy mentioning you here as I can't add you as a reviewer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything else seems good. Just one small change I have mentioned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Checks are failing due to unused variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
awesome, thank you for merging and releasing it! |
Fixes #54.
This PR introduces a new feature that allows setting the
short_name
parameter in themanifest.json
file independently from thename
parameter for web configurations.Currently, the
app_name
parameter is used to set bothname
andshort_name
in themanifest.json
file. With this change, we split theapp_name
parameter intoapp_name
andshort_app_name
to provide more flexibility.The
short_app_name
parameter is optional, and if not provided, it will default to the value ofapp_name
.Note:
The error codes and messages used in the catch blocks are not actually used in the codebase. Please advise if these should be removed or if there are any plans to utilize them in the future.