[MGNLUI-2854] i18n is not supported by all multi value field transformer Created: 25/Mar/14  Updated: 29/Sep/22  Resolved: 20/May/14

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

Type: Improvement Priority: Critical
Reporter: Diana Racho Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: controls, dialog, i18n, maintenance, multi-value, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-2871 Enhance the behavior of complex fields 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:
Epic Link: I18n fields issues

 Description   

Why is i18n support explicitly disabled for multi value properties?

MultiValueChildrenNodeTransformer.hasI18NSupport()

{ return false; }

 Comments   
Comment by Eric Hechinger [ 02/Apr/14 ]

Currently we provide i18n support for the default multi value field transformer (MultiValueTransformer) and some basic transformer (MultiValueChildNodeTransformer, MultiValueJSONTransformer ).

Unfortunately some more complex transformer like MultiValueChildrenNodeTransformer who store each value into sub nodes do not have this feature yet.

Comment by Eric Hechinger [ 20/May/14 ]

This issue is solved by MGNLUI-2871.
If you may want to support i18n for multi-field, you will need to use the new delegating transformers.
Documentation page will be added in ref of this ticket as soon as this document page will be reviewed.

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