Innei
@djyde For translation contributors or maintainers, it is indeed better to write all translations in the same file. But imagine if a json has thousands of lines and there are...
If you agree with this, I would move the root resource to namespaces/app
Also, for the sake of app loading speed, we don't load all the language resources. But by splitting the namespaces, we load the common resource for all languages, but not...
@djyde I've refactored it and resolved the code conflicts
@djyde And, we added the eslint rule to ensure that the order of each json is sortable. Fixed a bug in hmr where it would automatically switch back to default...
> It seems that it breaks [lokalise/i18n-ally](https://github.com/lokalise/i18n-ally/) preview feature. Which feature? I can't use i18n-ally, the namespace breaks them. This is a known issue. https://github.com/lokalise/i18n-ally/issues/1201
But, this file structure is supported.  https://github.com/lokalise/i18n-ally/wiki/Path-Matcher I don't know why it not work.
Resolved conflicts again.
Resolved conflicts again.
Understand what you're saying. For example, in xcode projects also use flat key-value pairs, and the famous open source project AFFiNE is similar. https://github.com/toeverything/AFFiNE/blob/4ac9bd7790eeea7e0660861432caa17a0337bd26/packages/frontend/i18n/src/resources/en-US.json @djyde I'd like to hear what...