Internationalization of WebApp Elements #270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o complexity of the information setting)
…ught to be boring
PabloGOP
added
enhancement🆕
Closed
|
PBC003
approved these changes
Apr 10, 2024
PabloGOP
changed the title
alagoconde
approved these changes
Apr 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
As of now, I've updated every page and test except for:
As these sections require special attention as they utilize data from an external source. I'll be addressing them promptly.
How to use
Pages with Internationalization:
t("key_of_jsons_message")to insert strings.key_of_jsons_messageis correctly set in allwebapp/src/localize/*.jsonfiles.Pages without Internationalization:
useTranslation.tin the component:const { t } = useTranslation();