[MAGNOLIA-6488] Improve key generator for templates Created: 08/Jan/16  Updated: 15/Mar/16  Resolved: 20/Jan/16

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

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

Issue Links:
dependency
is depended upon by MGNLEESOLR-40 Hardcoded labels and descriptions in ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Epic Link: Introduction of new i18n
Sprint: Kromeriz 27
Story Points: 2

 Description   

RenderableDefinitionKeyGenerator currently generates keys as templates.areas.name, templates.components.name

  • Key generator should generate specific keys for pages (templates.pages.name).
  • It could generate the second key with module prefix (moduleName.templates.areas.areaName).


 Comments   
Comment by Roman Kovařík [ 21/Jan/16 ]

For release notes:
Possibility to use new i18n (located in mgnl-18n folders). No need to use these properties for templates:

  • i18nBasename, title, description

The keys for title and description are auto generated:
For template with ID: moduleName:templates/pages/pageName

  • templates.pages.pageName or
  • moduleName.templates.pages.pageName
Generated at Mon Feb 12 04:15:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.