-
Notifications
You must be signed in to change notification settings - Fork 293
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
Text extractions menu is not working correctly #1112
Comments
Hey there, I'm facing the same issue with the text extractions menu not working on VS Code Version 1.87.2 and Windows 10 using "i18n Ally (v2.12.0)." The problem started right after updating to 1.87.2. I downgraded to 1.85, and the plugin worked again. Seems like there might be a compatibility issue with the latest VS Code update. Hopefully, this information helps in troubleshooting the problem. Looking forward to a compatibility fix soon 👍 |
Describe the bug
I was happy using this extension which made my life easier regarding localization. One of the features that I most used is the text extraction feature. Now when I extract text from the code the menu is not rendered correctly, the behaviour is different when I type a key starting with
Home
and when not. See the screenshots below.Content of the file
./messages/en.json
:Extension Version
i18n Ally (v2.12.0)
Framework/i18n package you are using
Next.js 14 / next-intl
To Reproduce
Steps to reproduce the behavior:
Home.
Device Infomation
Extension Log
Go to
View
->Output
->i18n Ally
, and paste the content below. You should mask any sensitive informationScreenshots
When typing any key not starting with
Home.
:When typing a key starting with
Home.
:The text was updated successfully, but these errors were encountered: