Replies: 2 comments
-
So at least i got the serialization working now with following the docs with
But still having to add all namespaces manually still seems to be cumbersome. |
Beta Was this translation helpful? Give feedback.
-
Having a custom localeStructure that is not listable requires also to have the ns option defined. v13.0.3 will error now if not done so. |
Beta Was this translation helpful? Give feedback.
-
Hi,
i am having a hard time figuring out how to change the path and filename of the translation file.
I tried both options described in the docs but both do not seem to work.
Desired output is:
public/locales/{namespace}.{locale}.json
I am using
localeStructure
So i left localPath on default and changed localeStructure
i18next-parser.config.js:
This works only if i also keep files in the default dirs like:
public/locales/de/common.json
then it would pick up values from:
public/locales/common.de.json
If only having the latter it says:
i18next::translator: missingKey de common header.logo.claim header.logo.claim
But files should not be double, this feels rather wrong.
localePath
I added a function as localePath adn i receive other errors;
Yields this error:
Adding a namespace list manually somewhere feels also rather wrong.
And even if i add
ns: ['common'],
i get another error:What am i missing here?
Beta Was this translation helpful? Give feedback.
All reactions