[MGNLUI-2565] Special field labels don't adhere to the newer i18n standards Created: 10/Jan/14  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: forms
Affects Version/s: 5.2.1, 5.4.8, 5.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Kars Blom Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-1548 Remove/inline FormItem and related su... Closed
causality
relation
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Field definitions like MultiValueFieldDefinition and LinkFieldDefinition have special labels that don't adhere to the new i18n standards. This forces the developer to currently set the deprecated i18nBasename in order to use custom i18n keys in those labels.

Example properties:
MultiValueFieldDefinition.buttonSelectAddLabel
LinkFieldDefinition.buttonSelectNewLabel



 Comments   
Comment by Mercedes Iruela [ 21/Nov/16 ]

Same behaviour for:

MultiValueFieldDefinition:

  • buttonSelectNewLabel
  • buttonSelectOtherLabel
  • buttonSelectAddLabel

LinkFieldDefinition:

  • buttonSelectNewLabel
  • buttonSelectOtherLabel
Comment by Roman Kovařík [ 11/Mar/21 ]

Works on the latest https://demo.magnolia-cms.com

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