Fix i18n handling of namespaces with spaces in #3281
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.
i18next recently added a 'natural language detection' feature that, whilst the details are irrelevant, broken the ability to have message catalog namespaces that contain a space.
This was introduced in a major version change on their part, but unfortunately their migration guide did little to highlight the impact of this feature. It did at least, once the dots were joined, point to the config options needed to disable the behaviour and get back to how it used to work.