Changelog History
Page 12
-
v19.2.0 Changes
February 19, 2020- โ Add ability to use commas in nested keys 1398
-
v19.1.0 Changes
January 27, 2020- โ explict warning when no languageDetector is used and no lng is defined 1381
- โ Add option to always format interpolated values 1385
- pass all options to format function 992#issuecomment-577797162
-
v19.0.3 Changes
January 06, 2020- ๐ fixes retry interval in backend connector 1378
-
v19.0.2 Changes
December 12, 2019- typescript: Type ResourceStore 1366
-
v19.0.1 Changes
November 19, 2019- ignore non valid keys in saveMissing 1359
-
v19.0.0 Changes
October 29, 2019- 0๏ธโฃ typescript: Typescript use
export default
for esm-first approach 1352
- 0๏ธโฃ typescript: Typescript use
-
v18.0.1 Changes
October 26, 2019- ๐ check loadedNamespace only once per lng-ns inside using
t
for better performance
- ๐ check loadedNamespace only once per lng-ns inside using
-
v18.0.0 Changes
October 24, 2019๐ When calling
i18next.changeLanguage()
bothi18next.language
andi18next.languages
will be set to the new language after callingloadResources
-> means when accessingt
function meanwhile you will get still the translations for the previous language instead of the fallback.When is this breaking? this does not break any current test - but if you depend on accessing i18next.language or i18next.dir during language change and expect the new language this will break your app.
๐ Reasoning: In react-i18next we get in a not ready state for loaded translations while we would prefer just waiting for the new language ready and trigger a rerender then - also a triggered rerender outside of the bound events would end in Suspense...
How can I get the language i18next will be set to?
i18next.isLanguageChangingTo
is set to the language called
-
v17.3.1 Changes
October 24, 2019- typescript: Add missing
cleanCode
option to TypeScript def 1344
- typescript: Add missing
-
v17.3.0 Changes
October 21, 2019- pass used language & namespace to postprocessor 1341