[MGNLUI-6305] Provide 6 UI port for MultiValueChildNodeTransformer Created: 09/Oct/20  Updated: 05/Mar/21  Resolved: 05/Mar/21

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

Type: Bug Priority: Neutral
Reporter: Šimon Demočko Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 55m
Original Estimate: Not Specified

Attachments: PNG File Deprecated Without direct replacement.png    
Issue Links:
duplicate
duplicates MGNLUI-5186 Provide 6 UI port for MultiValueChild... 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
Date of First Response:
Epic Link: MultiFields compatibility

 Description   

acceptance criteria

Introduce info.magnolia.ui.editor.MultiFormView.EntryResolution extender, that will resolve multi items as properties.

Why MultiValueAsMultipleProperties cannot be used

MultiValueAsMultipleProperties ItemProvider was thought that it could simulate similar behavior. I checked, it doesn't. What is necessary to achieve properties persisted under a multi-field is a different EntryResolution mechanism. Using current EntryResolution mechanisms with MultiValueAsMultipleProperties does not help, since MultiValueAsMultipleProperties is a CurrentItemProvider extension, thus, items are resolved to root and are not stored within a multi-field root, as is necessary for MultiValueAsMultipleProperties



 Comments   
Comment by Viet Nguyen [ 05/Mar/21 ]

Closed as duplication of MGNLUI-5186.

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