Skip to content

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

stephenhand
Copy link
Collaborator

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

  • Corresponding issue has been opened
  • New tests added
  • Feature flags added
  • Strings are localized
  • Tested for chat contacts
  • Tested for call contacts

Other Related Issues

None

Verification steps

AFTER YOU MERGE

  1. Cut a release tag using the Github workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
  2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
  3. Only then move the ticket into the QA column in JIRA

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

@stephenhand stephenhand requested review from GPaoloni and mythilytm May 6, 2025 19:43
Copy link
Collaborator

@mythilytm mythilytm left a 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" }
]
Copy link
Collaborator

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.

Copy link
Collaborator Author

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 },
);
};
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants