-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is a mismatch in next-i18next #996
Comments
Investigating this further, I still don't see a connection to my change. #926 was an enhancement only to the "custom" framework, which the configuration in this issue does not appear to be using. The release also included this change #941, which modified editor and core key detection code. This seems more likely related. If there's something I'm missing, let me know and I can continue to look into it. |
@terales I checked working with below settings. {
"i18n-ally.enabledFrameworks": [
"react-i18next"
],
"i18n-ally.namespace": true,
"i18n-ally.keystyle": "nested",
}
|
Describe the bug
There is a mismatch in next-i18next
Extension Version
i18n Ally v2.11.0
Framework/i18n package you are using
next-i18next
To Reproduce
Device Infomation
Extension Log
Go to
View
->Output
->i18n Ally
, and paste the content below. You should mask any sensitive informationScreenshots
The text was updated successfully, but these errors were encountered: