-
Notifications
You must be signed in to change notification settings - Fork 10
CHI-3259: language select poc #2955
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
base: master
Are you sure you want to change the base?
Conversation
…lts going blank. Fix orphaned case check
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.
I did not review the case related code.
Looks good assuming we address where to store flexUILocales.json and Substitutions.json
{ "label": "English", "aseloLocale": "en-US" }, | ||
{ "label": "Thai", "aseloLocale": "th-TH" }, | ||
{ "label": "Español", "aseloLocale": "es-CL" } | ||
] |
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.
Instead of hrm-form-definitions/form-definitions/as/v1/flexUiLocales.json
, I think it will be good to have this in the hrm-form-definitions/form-definitions/as/v1/customStrings/
folder.
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.
I considered that, but they aren't custom strings really, just another config setting
<Translator manager={Flex.Manager.getInstance()} translateUI={translateUI} key="locale-selector" />, | ||
{ align: 'end', sortOrder: 0 }, | ||
); | ||
}; |
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.
Nice!
Description
Rough POC for language select. Configured via a new json in the form definitions fold
One major missing feature is a notification telling the user to reload the page. Also proper UX is required to go to production
Can be merged because having an empty config switches it off
Checklist
Other Related Issues
None
Verification steps
AFTER YOU MERGE
You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P