i18n-ally
i18n-ally copied to clipboard
There is no expected work in vscode
Describe the bug
After vsCode installed the plug-in, the plug-in did not run as scheduled, the plug-in panel was empty, and there was an error running the plug-in command manually
Extension Version
v2.8.1
Framework/i18n package you are using
vue-i18n
To Reproduce Steps to reproduce the behavior:
- Install the i8N-ally plug-in in VScode
- Open the project ( vue3 + ts + vue-i18n 9.x )
Device Infomation
- OS: macos
- Version: 10.15
- VS Code Version: 1.63.0 (Universal)
Extension Log
🈶 Activated, v2.8.1
――――――
💼 Workspace root changed to "/Users/primewed/Desktop/code/trident/settlity-new-web"
🌞 Enabled
🧩 Enabled frameworks: Vue, VS Code
🧬 Enabled parsers: json
📈 Telemetry id: 69b171e3-6519-45cd-bbdb-3b5556468c86
🚀 Initializing loader "/Users/primewed/Desktop/code/trident/settlity-new-web"
Screenshots
An error occurred running the command manually. Procedure
My directory structure:
Looks like your issue is similar to but slightly different than mine, #701.
zh_CN
isn't a valid BCP47 language code so it's likely failing the same way as when I stick a test
directory in. zh-CN
would be valid.
In your case though I think you do have an alternative. If you change the "Language Tag System" to "legacy" I think zh_CN
will work with i18n Ally.
Thank you for your answer, but the problem is still the same after I try to change zh_CN
to zh-CN
Later, I tried to rename the “Language Tag System” to legacy
as you said, but it still cannot be recognized normally
Looks like your issue is similar to but slightly different than mine, #701.
zh_CN
isn't a valid BCP47 language code so it's likely failing the same way as when I stick atest
directory in.zh-CN
would be valid.In your case though I think you do have an alternative. If you change the "Language Tag System" to "legacy" I think
zh_CN
will work with i18n Ally.