i18n keys: As a developer I don’t have to define i18n keys for every translatable item, if they follow the convention, so that the process is less redundant and error prone (MGNLUI-1826)

[MGNLUI-2000] Use new i18n API in AppLauncher Created: 30/Aug/13  Updated: 04/Oct/13  Resolved: 02/Oct/13

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

Type: Sub-task Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:
Sprint: 5.1 Beta1- Frontend, 5.1 - Final

 Comments   
Comment by Christoph Meier [ 04/Sep/13 ]

Keys should include modulename and ".app"

Comment by Jozef Chocholacek [ 05/Sep/13 ]

Added the .app part.

There is no way to obtain a "parent" module for an AppDescriptor (except for a JCR query like select * from nt:base where jcr:path like '/modules/%/apps/%' and name = $APPNAME). I don't think it makes sense to do that, as the app names are unique, so the $APPNAME.app[.label] key should be unique enough.

Comment by Aleksandr Pchelintcev [ 02/Oct/13 ]

I18NIzer is injected in AppLauncherViewImpl but never used there.

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