-
Notifications
You must be signed in to change notification settings - Fork 296
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
Bug with nested jsons #345
Comments
May I have your config? |
|
I am seeing no problem with the example https://github.com/antfu/i18n-ally/tree/master/examples/by-frameworks/react%2Bi18next Can you share me a minimal reproduce repo? Thanks |
I experience the same issue. Everything seems to be fine, all translations are detected and shown in the editor. Then I attempt to update a translation from within the editor, and after accepting the change via "enter", it appends a non-nested string to the end of the json file and from now on does not detect any nested translation correctly. What am I missing? "i18n-ally.keystyle": "nested", |
Having exact same issue as originally described, same steps to reproduce. Framework is vue-i18n. @Yalian Did you find a solution? |
no :s,I ended up stopping using the tool, and used traduora for the translations and it serves me for multiple projects |
I also faced this same issue today. But when I change the key style both in user and workspace settings in Vscode it was solved. Initially, I only changed this setting in user settings. |
Describe the bug
when you have the translations in nested json, and you want to translate from the code, and the key is for example
"example.user"
instead of putting it as an object in the json, it puts it exactly the same as"example.user": ""
Extension Version
Framework/i18n package you are using
To Reproduce
"example": {"user": ""} "
Device Infomation
Extension Log
Go to
View
->Output
->i18n Ally
, and paste the content below. You should mask any sensitive informationScreenshots
![Peek 2020-07-06 21-05](https://user-images.githubusercontent.com/28605214/86689409-91e29280-bfcc-11ea-9095-3a0bd41e38d3.gif)
The text was updated successfully, but these errors were encountered: