Skip to content

Consider setting the default for returnNull to false in next major version (v23.0.0) #1884

@adrai

Description

@adrai

Seems for TypeScript users (in combination with react) it would be better to set the returnNull value to false by default.

i18next/react-i18next#1559
i18next/react-i18next#1576
i18next/react-i18next#1574
i18next/next-i18next#1795
i18next/next-i18next#2038
i18next/next-i18next#2059
https://stackoverflow.com/questions/70914886/react-i18n-t-function-doesnt-accept-string-variables-typescript-no-over/74817767
https://stackoverflow.com/questions/74146925/im-having-issues-with-i18next-in-react-18/74811575
https://stackoverflow.com/questions/74143213/how-to-handle-i18next-new-type-defaulttfuncreturn/74808715

Let's keep returnEmptyString set to true by default (not necessary regarding TypeScript issues)

image

I would say as soon as @pedrodurek reviewed (and maybe corrected/optimized) the latest TypeScript changes and issues, we'll go for a new major release that changes the defaults, this would maybe simplify the usage for TypeScript users.

TODO before next major release

TODO

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions