Closed jrock2004 closed 2 years ago
Should work...as de work it must be related to your fr, sp JSON files I guess...invalid JSON?
Anyway 100% related to your code and not an issue in this module...without a reproducible example there is not much we can do to help you with this...
@jamuhl When I run my FR json file thru validator it passes. Could it be something with a value?
Not really...try setting debug: true
on i18next init...eventual it gives you some warnings in the browser console.
const resources = {
de: {
translation: de,
},
en: {
translation: en,
},
fr: {
translations: fr,
},
sp: {
translations: sp,
},
};
see namespace naming -> fr, sp ---> translations instead of translation
Ughhhh, thanks @jamuhl
🐛 Bug Report
So I am trying to understand why my fr and sp languages are not being used and the fallback is being used. de works just fine for me so not sure what I did wrong with other languages
To Reproduce
A minimal reproducible example. A codesandbox example or similar or at least steps to reproduce the behavior:
Expected behavior
I expect that when I load up
http://localhost:9000?lng=fr
that it will be in frenchYour Environment