Skip to content
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

@property doesn't work correctly with defaultValue for localizable strings #3502

Closed
andrewtelnov opened this issue Oct 17, 2021 · 0 comments · Fixed by #3503
Closed

@property doesn't work correctly with defaultValue for localizable strings #3502

andrewtelnov opened this issue Oct 17, 2021 · 0 comments · Fixed by #3503
Labels
Milestone

Comments

@andrewtelnov
Copy link
Member

We can't use defaultValue for declearing localizable properties. A new attribute defaultStr has been introduced. Here is the example of using:

@property({ localizable: { defaultStr: "confirmRemoveFile" } }) confirmRemoveMessage: string;

This code will create localizable property and get the default value from localizable strings using the function in the gettter, istead of setting the default value from localization property on creating object.

@andrewtelnov andrewtelnov added this to the v1.8.73 milestone Oct 17, 2021
@andrewtelnov andrewtelnov added this to Incoming in Current sprint progress via automation Oct 17, 2021
@andrewtelnov andrewtelnov changed the title @property doesn't work correctly with defaultValue for localable strings @property doesn't work correctly with defaultValue for localizable strings Oct 17, 2021
Current sprint progress automation moved this from Incoming to v1.8.73 Oct 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant