Type errors when using custom contextSeparator

[giovannipiller]

🐛 Bug Report

When contextSeparator has been customized, types will be broken when using a t function providing a context.

The error will be something like this: Type at position 1 in source is not compatible with type at position 1 in target.

To Reproduce

Your i18n config must have contextSeparator: '|'

// the namespace – custom.json

{
  "example": "Example",
  "example|custom": "Example with context"
}

// the react component

const { t } = useTranslation(['custom']);

// this would result in a type error, `myValue` is `never`
const myValue = t('custom:example', { context: 'custom' });

@marcalexiei will open a PR with a fix and an additional test case.

Expected behavior

There are no type errors when using a custom contextSeparator.
i.e. by adding a way to override the default contextSeparator used by types.

Your Environment

• runtime version: node v18
• i18next version: i.e. 23.4.2
• os: macOS 13.4.1

[adrai]

Should be addressed by @marcalexiei in v23.4.3.