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
After we have removed Angular, we should explore the possibility of having the t function of i18next be typed according to en.json. https://www.i18next.com/overview/typescript
This way, we could ensure we never try to access a key that doesn't exist. It would also work with IntelliSense to give us autocompletion for existing keys.
We would need to:
upgrade to latest i18next and react-i18next
enable strictNullChecks in our tsconfig.json (a good idea anyway and more achievable now than several months ago)
After we have removed Angular, we should explore the possibility of having the
t
function ofi18next
be typed according toen.json
. https://www.i18next.com/overview/typescriptThis way, we could ensure we never try to access a key that doesn't exist. It would also work with IntelliSense to give us autocompletion for existing keys.
We would need to:
i18next
andreact-i18next
strictNullChecks
in ourtsconfig.json
(a good idea anyway and more achievable now than several months ago)types/i18next.d.ts
:The text was updated successfully, but these errors were encountered: