i18next
Can't parse namespace from getFixedT usage
🐛 Bug Report
Looking at the documentation and different issues I found, especially this one (https://github.com/i18next/i18next-parser/issues/703#issuecomment-1327896105), it seems that using i18n.getFixedT should help specify a single namespace for a whole file.
To Reproduce
I managed to craft a minimal reproduction repo here
Expected behavior
What I'm looking for behind this feature of getFixedT is to be able to specify a t function for a whole file, without repeating the namespace name at each function usage.
For instance, with a file defining lots of metadata for my app:
const t = i18n.getFixedT(null, "myFileNameSpace")
const DATA = [
{
name: t("item1.name"),
description: t("item2.description"),
},
{
name: t("item2.name"),
description: t("item2.description"),
},
]
I'd like the parser to extract a myFileNameSpace.json containing the keys specified. Instead, the keys are extracted in the default namespace.
Your Environment
- runtime version: i.e. node v18, browser Chrome, latest version
- i18next version: 23.10.1
- i18next-parser version: 8.13.0
- os: Mac
I'm having the same issue. It would be nice if we can get some info about this.
Hitting this issue as well, which forces me to specify the namespace for each translated string:
i18n.t("item1.name", {
ns: "myFileNameSpace",
defaultValue: "Default value",
})
