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
Currently, packages use their own language files for translation. These files contain the same information from one package to another, it creates a kind of redundancy and it is difficult to maintain or update
🙂 Expected behavior
It will really be interesting to be able to use the internal mono-repo package containing all the languages that we can import in the different packages/apps of mono-repo as dependence
e.g:
...
├── packages
| ...
│ ├── @ever-platform-tranlation // contains json data of languages (maybe other useful helpers)
│ ...
│ ├── shop-mobile-ionic // import @ever-platform-tranlation as dependecy
│ └── shop-web-angular // import @ever-platform-tranlation as dependecy
...
The text was updated successfully, but these errors were encountered:
Neosoulink
changed the title
Improvement of language accessibility for the translation using the mono-repo power
refactor: improvement of language accessibility for the translation using the mono-repo power
Feb 5, 2022
Neosoulink
changed the title
refactor: improvement of language accessibility for the translation using the mono-repo power
feat: improvement of language accessibility for the translation using the mono-repo power
Feb 5, 2022
Structure improvement
🔎 Search Terms
🤔 Actual behavior
Currently, packages use their own language files for translation. These files contain the same information from one package to another, it creates a kind of redundancy and it is difficult to maintain or update
🙂 Expected behavior
It will really be interesting to be able to use the internal mono-repo package containing all the languages that we can import in the different packages/apps of mono-repo as dependence
e.g:
The text was updated successfully, but these errors were encountered: