compatibilityJSON = 'v3'
on i18next init call.skipOnVariables
option now is set to true.
To enforce old behaviour you can set skipOnVariables = false
on i18next init call.nsSeparator
or keySeparator
option to false
.
In case you want to skip this natural language detection, provide a keySeparator
and/or a nsSeparator
option.whitelist
to supportedLngs
nonExplicitWhitelist
to nonExplicitSupportedLngs
languageUtils.isWhitelisted
to languageUtils.isSupportedCode
i18next.resolvedLanguage
property, that represents the current resolved language. It can be used as primary used language, for example in a language switcher.ns
option, the defaultNS
will, by default, be set to the first ns passed.i18next.changeLanguage()
both i18next.language
and i18next.languages
will be set to the new language after calling loadResources
-> means when accessing t
function meanwhile you will get still the translations for the previous language instead of the fallback.i18next.isLanguageChangingTo
is set to the language calledi18next.init().on()
anylonger.compatibilityAPI: 'v1'
flag won't do anything anymore.nonExplicitWhitelist
flag was changed to be used in user detected language too, before it was restricted to defined fallback languages only.compatibilityJSON = 'v2'
on i18next init call.i18next.init({ getAsync: false });
i18n.noConflict();
i18n.t('myKey', { indefinite_article: true })