i18n: Remove initial language check #629
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
This language check caused the defaultLocale to always be set when reloading the page instead of using the detection mechanism. It previously worked because the config used in the i18n file was from chaire-lib-common, which was imported before getting the actual config from chaire-lib-frontend. When correctly importing the frontend config, or if setting default values for the languages in the common config, the issue arose.
kaligrafy
approved these changes
Mar 28, 2023
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.
This language check caused the defaultLocale to always be set when reloading the page instead of using the detection mechanism. It previously worked because the config used in the i18n file was from chaire-lib-common, which was imported before getting the actual config from chaire-lib-frontend. When correctly importing the frontend config, or if setting default values for the languages in the common config, the issue arose.