[MAGNOLIA-6535] I18n Key generators should be consistent Created: 05/Feb/16  Updated: 23/Feb/16  Resolved: 16/Feb/16

Status: Closed
Project: Magnolia
Component/s: i18n, rendering
Affects Version/s: None
Fix Version/s: 5.4.5

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 1.5h
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLUI-3764 I18n: I can reuse the keys between mo... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Introduction of new i18n
Sprint: Kromeriz 31
Story Points: 5

 Description   

Currently every I18nKeyGenerator generates different set of keys. This is not documented and and consistent.
AbstractI18nKeyGenerator should take care of generating less specific keys.
We should still support currently generated keys (if possible).



 Comments   
Comment by Roman Kovařík [ 05/Feb/16 ]

For release notes and docu:
The i18n keys are now consistent:

  • Template: id=moduleName:components/componentName
    • moduleName.templates.components.componentName.title
    • templates.components.componentName.title
  • Templates without IDs (usually areas)
    • templates.areas.areaName.title
Generated at Mon Feb 12 04:15:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.