[MGNLUI-2080] Fix MessagesUtil.getKey usage for those which require a specific i18n basename Created: 12/Sep/13  Updated: 17/Sep/13  Resolved: 13/Sep/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.1

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
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 MGNLUI-2045 create new message-bundles each for e... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Sprint: 5.1 Beta1- Frontend, 5.1 - RC1

 Description   

fix MessagesUtil.getKey()-usage for those who require now a specific i18n-base-name
... this is more a workaralund then proper usage of the new i18n-API.
we may change that later on.



 Comments   
Comment by Jozef Chocholacek [ 16/Sep/13 ]

Please define the bundle name ("info.magnolia.ui.admincentral.messages") as a constant.

Comment by Christoph Meier [ 16/Sep/13 ]

all* bundles have been set-up and filled with key-value-pairs.
See http://wiki.magnolia-cms.com/pages/viewpage.action?pageId=72974954#i18nStoryOverviewStatus-MessageBundlestobedone, too.

*) standard-templating-kit has no bundle yet, but for the release i set this ticket to fixed now. STK should rely on "old-stuff"-fallback-mechanisme meanwhile

to be relase-ready, this ticket will get the status "fixed", although STK hasn't its proper bundle, yet

Comment by Federico Grilli [ 16/Sep/13 ]

I'd prefer keeping "info.magnolia.ui.admincentral.messages", as it is a temporary solution as long as we don't have a proper replacement for MessagesUtil.get(..). Furthermore, it makes it easy to search for usages of that string once we will want to get rid of it.

Generated at Mon Feb 12 08:53:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.