[MGNLUI-3354] Generate i18n keys not referencing module name or id for forms and actions Created: 19/Feb/15  Updated: 06/Aug/15  Resolved: 19/Feb/15

Status: Closed
Project: Magnolia UI
Component/s: actionbar, forms, pages app
Affects Version/s: None
Fix Version/s: 5.3.8

Type: Improvement Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLGS-99 Missing i18n messages on sitemap publ... Closed
duplicate
is duplicated by MGNLUI-3436 Missing i18n keys when DAM is configu... Closed
relation
is related to PAGES-9 Remove publishing-related i18n keys 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)
Date of First Response:

 Description   

This should allow us to use generic keys for generic actions and labels, such as workflow ones, instead of being forced to create i18n messages.properties for each module requiring them.
E.g. pages app defines pages.publish.message.content.repository=Workspace whereas it could simply be publish.message.content.repository=Workspace (of course, such keys should be moved to a more "generic" module than pages) and be reused by other modules. See also linked issue.


Generated at Mon Feb 12 09:05:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.