Sourced from react-i18next's changelog.
17.1.0
- feat(types): with i18next's new
parseInterpolation: 'icu'(or'mf2') type option (i18next v26.5.0), thevaluesofIcuTransandIcuTransWithoutContextare typed from the message ofi18nKey, like the options oft(): a misspelled argument, a value of the wrong type or a value meant for another key is a type error.valueswasRecord<string, any>before, and still is with any otherparseInterpolationsetting.valuesstays optional, as onTrans.useTranslation'standTransvaluesget the checks from i18next's types without changes here.- fix(types):
IcuTransandIcuTransWithoutContextnow infer the literali18nKey(consttype parameter, asTransdoes), so props that depend on the key are checked against that key instead of all keys of the namespace.
d3b1236
17.1.0efed87d
chore: i18next ^26.5.0 for the parseInterpolation 'icu' / 'mf2' type
tests6300ae2
feat(types): IcuTrans values typed from the message under
parseInterpolation ...