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
Describe the bug
I have a project structure like this
app1
| - lang
| - - {locale}.json
app2
| - lang
| - - {locale}.json
shared
| - lang
| - - {locale}.json
Thus, every locale file, like "en.json" exists multiple times.
Relevant settings are
pathMatcher: "{locale}.json"
localesPaths: ["**/lang"]
targetPickingStrategy: "most-similar"
Translations previews in the IDE and in the sidebar work, also opening the editor UI works.
When changing any translation in the editor I am always prompted for the translation file.
However, every translation key is unique and the editor could remember where it read the data from and use the same file.
Extension Version
v2.12.0
Framework/i18n package you are using
vue-i18n
To Reproduce
Steps to reproduce the behaviour:
Setup multi-app repository with shared translations
Translations are detected and previewed in the IDE
When opening the editor and updating any translation, I'm prompted for the translation file
If you can point out where the issue might resolve from, I am happy to contribute to a fix.
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a project structure like this
| - lang
| - - {locale}.json
| - lang
| - - {locale}.json
| - lang
| - - {locale}.json
Thus, every locale file, like "en.json" exists multiple times.
Relevant settings are
Translations previews in the IDE and in the sidebar work, also opening the editor UI works.
When changing any translation in the editor I am always prompted for the translation file.
However, every translation key is unique and the editor could remember where it read the data from and use the same file.
Extension Version
v2.12.0
Framework/i18n package you are using
vue-i18n
To Reproduce
Steps to reproduce the behaviour:
If you can point out where the issue might resolve from, I am happy to contribute to a fix.
The text was updated successfully, but these errors were encountered: