Filter out languages that aren't RFC5646-shaped #613
Merged
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.
I wanted to try Phanpy, but only got a blank page, because
Intl.DisplayNames
can't handle some values that might appear innavigator.languages
.As MDN says:
My config includes
*;q=0.5
as the last value, which gives anavigator.languages
like['xx', 'xx', 'xx', 'xx', '*']
.results in
RangeError: Incorrect locale information provided
.So this proposed fix filters out any language tags that don't look like RFC 5646/BCP 47 format, which is what
Intl.DisplayNames
accepts.It's not a full validator, but it does not exclude any valid tags.