New issue
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
Add support to proper augment PluginOptions type #1583
Conversation
Would also other backends need to be updated? or other plugins like: https://github.com/i18next/i18next-browser-languageDetector ? |
I'm going to take a look at the other repos. |
Hey @adrai, let me know if there any remaining plugins. |
No problem!!! Yeah, it should have no breaking changes on both sides |
@pedrodurek , hmm, looks like you broke support of
|
Hey @mrrotberry, yeah, It was reported yesterday, I'm on it! 😃 |
OK, sorry didn't see 😃 could you tell me where this issue was discussed and where I could keep track of it?) |
thank you very much and have a nice day) |
@mrrotberry should be fixed with the new i18next-chained-backend version |
@adrai I confirm, the typing works fine, there are no errors. Thank you very much 👍 |
You have to thank @pedrodurek |
This is the first PR that solves this problem: #1578
Another one will be created under
i18next-locize-backend
that depends on this.It should have no breaking changes to users.
Checklist
npm run test