Fix react-i18next(and next-i18next) framework integration

[SimeonC]

Fixing the react-i18next framework to extend the base i18next framework as there shouldn't be many differences between them.

Also added in the v4 plurals fixing #677 and #688

In the image below, i18n-a11y is detecting the file if I use a . but not if I use a : (the : here is correct as it's a namespaced file)

[ThenTech]

Can this be approved and merged? Having #677 and #688 would be good.

[Arno500]

Hello @SimeonC
Any updates on this?
Thanks for the fix :P

[SimeonC]

I'm unfortunately powerless to merge this. As far as I'm aware it's all correct and ready to merge.

[Arno500]

Oh alright, I thought it was to you to merge this. Sorry for the noise…

[Stefouch]

Can this be approved and merged? Having #677 and #688 would be good.

Get my upvote for this merge!
I have the same issue

[leon0399]

+1 for merge

Is project dead?

[boredland]

Has this change been released? I am a bit confused, as for me v4-style plurals don't seem to work and #688 is still open.

[aranard]

Is this project still being actively maintained? I'd like to contribute a feature that will help my team, and I'm running into issues getting the extension to build.

This seems to be in part because of this change being merged. The splitting of frameworks/react.ts into two separate files (react-i18next.ts and react-intl.ts) has broken code in frameworks/index.ts because that original file no longer exists (but is still being referenced):

Is this something anyone is actively aware of or looking into? Thanks.

[Swiftwork]

This PR does not seem to have been checked at all. Surely ReactI18nextFramework should be extending I18nextFramework and not Framework. I18nextFramework is also a default export and not a named one...

[Swiftwork]

This whole PR is broken and adds nothing to the extension except for supporting pluralization. It breaks imports, has the wrong usage patterns, and doesn't even add itself to the frameworks list. Please revert this PR and add the pluralization to the i18next framework instead.

'{key}_zero',
'{key}_one',
'{key}_two',
'{key}_few',
'{key}_many',
'{key}_other'

[graup]

I've found maintainers only reply here if you send them a request through Lokalise customer support.