You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the language is set to cimode, the hasLoadedNamespace check always returns false for any given namespace, as i18next will never load any namespace when the language is cimode (early return in loadResources). This causes an infinite loop with react-i18next constantly trying to load the "missing" translation and always finding it to not be loaded once it's notified.
Occurs in react-i18next version
10.2.0
To Reproduce
Use any react-i18next component or hook while the i18next instance has lng: 'cimode' set.
Expected behaviour
Translations to be rendered according to the cimode behavior (just returns the keys as-is, optionally with a namespace prefix)
Screenshots
OS (please complete the following information):
Device: MBP 2018 15"
Browser: 72.0.3626.17
The text was updated successfully, but these errors were encountered:
If you like this module don’t forget to star this repo. Make a tweet, share the word or have a look at our https://locize.com to support the devs of this project -> there are many ways to help this project 🙏
Describe the bug
When the language is set to
cimode
, thehasLoadedNamespace
check always returnsfalse
for any given namespace, as i18next will never load any namespace when the language iscimode
(early return inloadResources
). This causes an infinite loop withreact-i18next
constantly trying to load the "missing" translation and always finding it to not be loaded once it's notified.Occurs in react-i18next version
10.2.0
To Reproduce
Use any
react-i18next
component or hook while thei18next
instance haslng: 'cimode'
set.Expected behaviour
Translations to be rendered according to the
cimode
behavior (just returns the keys as-is, optionally with a namespace prefix)Screenshots
OS (please complete the following information):
The text was updated successfully, but these errors were encountered: