[MGNLUI-5726] MultiField's ByIndexedChildNodes child resolution strategy always prepends node name Created: 12/Mar/20  Updated: 03/Apr/20  Resolved: 20/Mar/20

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

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Šimon Demočko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2.25d
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLRESTUI-24 CLONE - MultiField's ByIndexedChildNo... Closed
is cloned by MGNLPN-486 CLONE - MultiField's ByIndexedChildNo... Closed
Relates
relates to MGNLUI-5723 6.2 compatiblity layer does not suppo... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: UI Framework 20
Story Points: 5

 Description   

In old UI framework:

When multivalue is configured with DelegatingMultiValueSubnodeTransformer, subnodes are saved as indexes (0, 1, 2, ...)

In new UI framework:

Multivalue field name is always prepend before the index, for example (allVehicles0, allVehicles1, ...)

The use case for having just indexes as names comes from content-type apps, where DelegatingMultiValueSubnodeTransformer is used to save multivalue fields.

New UI framework uses resolution strategy to find children of multivalue fields. The strategy ByIndexedChildNodes always prepends the node name.


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