Open alexander-lebed opened 2 years ago
Thanks for report! I'll take a look
@alexander-lebed are there any changes in json file extensions? JSON v4 looks pretty much the same as older JSON formats, at least in it's structure. So my guess is that your json files have format other than 'json' or 'json5' which are supported by the plugin, so the plugin simply does not see them.
Got the same "Unresolved key" issue with the v4 pluralization keys. For example t('keyName', {count: 5})
shows error, but the translation works as expected.
Translation file example:
{
"keyName_zero": "{{count}} items",
"keyName_one": "{{count}} item",
"keyName_many": "{{count}} items"
}
Docs for reference: https://www.i18next.com/translation-function/plurals#languages-with-multiple-plurals
Thank you for an awesome plugin, I love it!
Recently I migrated my translation keys to new i18next JSON v4 format, but in WebStorm I cannot navigate to such keys anymore and shows it as Unresolved key.