fix: language picker fallback logic #16458
Open
+15
−4
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.
Description
When a language name is the same in both English and that language, logic treats this as if the translated form is not available for that locale, and falls back to the
Intl.DisplayName
JavaScript library. In certain cases this is undesired, such as with Tagalog, whose name is the same in English and Taglog, falls back to the JS library and results in "Filipino" (but we already have Filipino specifically.forceLocalName
to theI18nLocale
type (adding intellisense documentation for future clarity) to to override this and use the locale name instead"language-tl": "Tagalog",
to both en/common.json and tl/common.json filesRelated Issue