Override component translations
See original GitHub issueI would like to create translatable reusable component, but I cannot figure out how to override component default locales from global locales. Is it possible now? Like this maybe In component:
locales: {
en: { hello: 'world' },
}
In global locales:
en: { componentName: { hello: 'my world' } }
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Override Translations in Second-Generation Managed ...
You can override metadata translations for custom objects in namespaced unlocked packages and second-generation managed packages. For example, override the ...
Read more >Overriding frontend components - richie.education
Override an existing translation key. As explain above, the compilation process aggregates translations files then merges them according their ...
Read more >How to override a module translation? - Odoo
I would visit the structure of your inheritance. Make sure you have inherited the original module in a way that it will override...
Read more >How to override react-admin existing translation - Stack Overflow
Use the type TranslationMessages. So, remove Ra Object and add directly your translations export const messages : TranslationMessages = { .
Read more >Overriding Global Language Translations - Learn — Liferay
Liferay DXP/Portal implements headings, labels, and messages for the default locale and many other locales using language translations. You can override these ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kazupon another use case I currently face is that a few customers disagree with the way to translate a word.
Components translations is fantastic to keep the translations close to the need. Global translation could be a nice way to customise the translation when a subset of the users need to see something translated differently.
There is definitely a valid use case for this. Please reopen and reconsider this.