Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

3.1.1 Feature or Bug?

See original GitHub issue

Is it a feature, that only the first namespace should be passed?

Changelog.md states:

fixes issue in fixing t function - pass only first namespace not an array of namespaces

But this is not a minor change. It broke a lot of our translation.

We used it like:

export default translate(['namespace1', 'namespace2'])(Component);

Can you at least release it as major?

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:9 (8 by maintainers)

Top GitHub Comments

3reactions

jamuhlcommented, May 16, 2017

react-i18next@4.1.0

You can now translate(['ns1', 'ns2'], { nsMode: 'fallback' } to toggle that back to pre v4 behaviour (using passed namespaces as ordered fallbacks).

Or you can set that “globally” by i18next.init({ react: { nsMode: 'fallback' } });

3reactions

vpriemcommented, May 11, 2017

Hi jamuhl,

why not revert it as the next minor and do this as a major? We will not be the only one having this breaking change.

Anyway when I take a look at http://i18next.com/translate/namespace/#basic it seems to be a standard (and nice) feature to pass several namespaces and use the last one as a fallback, without having to prefix it. So honestly I don’t understand the benefit of that change/fix or do you mean this is an issue and you will provide a fix?

BTW: translate('namespace1') instead of translate(['namespace1') is nice and should be documented.