nsMode global configuration option

Did something change with 6.x? Formerly, I could pass multiple namespaces into translate and I could use them without prefixes, understanding that the first key found would win. Now it is not finding my key, but it will if I prefix it.

So, from the example in the docs:

function TranslatableView(props) {
  const { t } = props;
  return (
    <div>
      <h1>{t('keyFromDefault')}</h1>
      <p>{t('anotherNamespace:key.from.another.namespace', { /* options t options */ })}</p>
    </div>
  )
}

export default translate(['defaultNamespace', 'anotherNamespace'])(TranslatableView);

^^ works, but the following no longer does:

function TranslatableView(props) {
  const { t } = props;
  return (
    <div>
      <h1>{t('keyFromDefault')}</h1>
      <p>{t('key.from.another.namespace', { /* options t options */ })}</p>
    </div>
  )
}

export default translate(['defaultNamespace', 'anotherNamespace'])(TranslatableView);

This would state (something like my log message) translation missing 'key.from.another.namespace' for en 'defaultNamespace'. Am I missing a config option?

[rosskevin]

Thank you, this was my mistake.

I was looking here: https://www.i18next.com/configuration-options.html

And I should have been looking here: https://react.i18next.com/components/i18next-instance.html

I used the react addition to options and it works fine.

[jamuhl]

Just made a test: https://www.webpackbin.com/bins/-KvMK7GooEOLVwtqEzgq

app.js line 55 -> nsMode in translate options: works i18n.js line 40 -> nsMode in i18n options: works

(react-i18next@6.0.2)

Could you provide a webpackbin or more info where setting nsMode fails - seems i miss a case.