We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
returned value from parse breaks translation
if you use parse to process backend data .. it cause the t function to return missing key
simple example:
in init:
backend:{ loadPath: 'path to load', parse:(data: any) => { return{ En: { translation: { hello: "hello" } }, Ar: { translation: { hello: "مرحبا" } } } }
in component : t(hello) => missing key
although if you use the same returned object in 'resources' then it works ..
to work properly
A clear and concise description of what you expected to happen.
The text was updated successfully, but these errors were encountered:
Please provide a minimal but complete reproducible example repository or codesandbox... not just fragments of unformatted code snippets.
Sorry, something went wrong.
btw: your parse function returns the wrong data anyway... you should return the translation resources for a specific language and namespace......
No branches or pull requests
🐛 Bug Report
returned value from parse breaks translation
To Reproduce
if you use parse to process backend data .. it cause the t function to return missing key
simple example:
in init:
backend:{
loadPath: 'path to load',
parse:(data: any) => {
return{
En: {
translation: {
hello: "hello"
}
},
Ar: {
translation: {
hello: "مرحبا"
}
}
}
}
in component :
t(hello) => missing key
although if you use the same returned object in 'resources' then it works ..
Expected behavior
to work properly
A clear and concise description of what you expected to happen.
Your Environment
-i18next-htttp-backend version: ^3.0.1
The text was updated successfully, but these errors were encountered: