i18next/i18next-v4-format-converter

Doesn't work with custom pluralSeparator

Closed this issue ยท 1 comments

๐Ÿš€ Feature Proposal

Either implement a pluralSeparator option in the converter, or document that it won't work with custom options like that - in this README, in the online tool and in the docs (which were the places I saw).

Motivation

We use pluralSeparator: '^' as a way to avoid any weird issue with readable keys (as opposed to code-only keys). There's no tool to automatically convert from v3 to v4 in this scenario.

adrai commented

image

image

image