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-2014] Use new i18n API in Favorites (replace the old one) Created: 03/Sep/13  Updated: 17/Sep/13  Resolved: 17/Sep/13

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

Type: Sub-task Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Christoph Meier
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-5296 I18nizer: Pattern or API for unmodele... Open
supersession
is superseded by MGNLUI-2064 Create separate messages bundles for ... Closed
Template:
Date of First Response:
Sprint: 5.1 Beta1- Frontend, 5.1 - Final

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

changed in info.magnolia.i18n

  • FavoritesEntry
  • FavoritesForm
  • FavoritesGroup
  • FavoritesViewImpl
Comment by Christoph Meier [ 04/Sep/13 ]

fixed and pushed

Comment by Magnolia International [ 04/Sep/13 ]

We need a better solution for unmodeled/unconfigured texts. See MAGNOLIA-5296

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