Sourced from react-i18next's changelog.
17.0.16
- fix(Trans): a selector
i18nKeythat points into a secondary namespace ofuseTranslationnow resolves the same wayt()does. Withconst { t } = useTranslation(['ns1', 'ns2']),t($ => $.ns2.message)works since 17.0.7, but<Trans t={t} i18nKey={$ => $.ns2.message} />rendered the raw key (or its children).Transalways passed annsoption tot, filled fromt.ns(the primary namespace only), and an explicitnsmakes i18next's fixedtskip the hook's full namespace list (scopeNs). WhenTransorTransWithoutContextgets atthat carries its own namespace and nonsprop, it now leavesnsout and lets thattapply its own. String keys,keyPrefix,nsMode: 'fallback', an explicitnsprop andTranswithout atprop behave as before. Compatibility note: if the primary namespace has a nested object named like a secondary namespace (ns1→ns2.message),Transnow resolves$ => $.ns2.messagetons2:message, ast()already does. Fixes #1933.
606b6a5
17.0.1651b7c26
fix(Trans): resolve selector keys into useTranslation's secondary
namespaces0a2f018
fix(examples): load the Swedish file in test-jest and align the ru
plural tag...