Skip to content
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

official docs #17

Open
FDiskas opened this issue Mar 29, 2021 · 2 comments
Open

official docs #17

FDiskas opened this issue Mar 29, 2021 · 2 comments

Comments

@FDiskas
Copy link

FDiskas commented Mar 29, 2021

What is the main difference from official docs and this library?
https://react.i18next.com/latest/typescript

@DovydasNavickas
Copy link

Mostly, that official version only supports this since version v11.8.0. It was released 2020-12-07 and our library was released 2019-09-09, used for a year already. So, it's ~2 years older 😄

I see that we can use the same approach now that core library supports this.

Although one big advantage of typed-i18next is it fails your build during CI if you have missing keys in one of the languages and I'm not sure if we can achieve this with types-only approach.

@FDiskas
Copy link
Author

FDiskas commented Mar 29, 2021

Using type definition also typescript throws error if key is missing. This is why I landed here. Wanted to allow thous missing keys :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants