You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
HI! Using your library. I have types generation for my i18next to have autocompletion in LSP. And cant get right types for t function from useTransContext. I have 10 different namespaces and without autocompletion its a mess.
Your library have this type. Seems the problem is here.
Also key prop in Trans component have type of string. Which expected to be type of first argument of t function. That is not necessary for me but also would by a QOL improvement 🙏
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
HI! Using your library. I have types generation for my i18next to have autocompletion in LSP. And cant get right types for t function from
useTransContext
. I have 10 different namespaces and without autocompletion its a mess.Your library have this type. Seems the problem is here.
Its defaults to "translation" namespaces. Also in my case I have default namespace named "menu".
If I change types to
then I am getting expected behavior for t function.
I was trying to redeclare types for module but got error from TS
Error
What I get:
What I expect:
My custom types file
Does your library work with custom types? 🙏
The text was updated successfully, but these errors were encountered: