You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We used Figma plugin to create and upload keys to a service. The plugin uses Figma node id as keys, so the keys would be something like I1177:488994;8975:1945;8975:1876.
But this kind of key cannot be parsed correctly by i18n-ally in our tsx or ts files:
t('I1177:488994;8975:1945;8975:1876')
We found that if a key contains ;, it cannot be found as a key.
And if a key contains :, it can be recognized as a key, but does not match the right content in the i18n resource files.
Describe the bug
We used Figma plugin to create and upload keys to a service. The plugin uses Figma node id as keys, so the keys would be something like
I1177:488994;8975:1945;8975:1876
.But this kind of key cannot be parsed correctly by
i18n-ally
in ourtsx
orts
files:We found that if a key contains
;
, it cannot be found as a key.And if a key contains
:
, it can be recognized as a key, but does not match the right content in the i18n resource files.Extension Version
i18n Ally
v2.12.0
Framework/i18n package you are using
react-i18next
To Reproduce
src/i18n/en/translation.json
.vscode/setting.json
src/Test.jsx
test1:key
would not match content in translation file.test2;key
would not be considered as a key.test3:key
works well.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: