[MGNLUI-6223] MultiValueSubChildrenNodeTransformer needs to be ported to M6 UI so as not to break old categories app data Created: 21/Sep/20  Updated: 18/Jan/21  Resolved: 12/Jan/21

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

Type: Bug Priority: Neutral
Reporter: Šimon Demočko Assignee: Sang Ngo Huu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 6d 2.5h
Original Estimate: Not Specified

Attachments: PNG File CleanShot 2020-12-11 at 16.25.37.png    
Issue Links:
Issue split
split from MGNLUI-6190 Refactor dependencies for MGNLUI-6253... Closed
Relates
relates to MGNLCAT-187 Configure categories app to use Multi... Closed
causality
dependency
is depended upon by MGNLCAT-184 Migrate categories app to new UI FW Closed
is depended upon by MGNLDEMO-346 Migrate Tour Categories app to new UI... Closed
is depended upon by MGNLCAT-183 Implement categories app in new UI fr... Closed
documentation
to be documented by MGNLUI-6513 DOC: MultiValueSubChildrenNodeTransfo... 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
Documentation update required:
Yes
Date of First Response:
Epic Link: MultiFields compatibility
Sprint: UI FW 16, UI FW 17, UI FW 19
Story Points: 8

 Description   

See https://documentation.magnolia-cms.com/display/DOCS62/Transforming+field+values+-+5+UI#Transformingfieldvalues-5UI-Multivaluetransformers for an example of how data are stored with MultiValueSubChildrenNodeTransformer. Currently opening and closing would result in rewrite of how these data are stored, which could break customer's templates. We can't re-store this data to a different format and thus need a support for this transformer in M6. 

Later, this page will need to be updated with details on conversions: https://documentation.magnolia-cms.com/display/DOCS62/Magnolia+6+UI+ports+of+5+UI+field+transformer+classes 



 Comments   
Comment by Šimon Demočko [ 11/Dec/20 ]

DOC update: https://documentation.magnolia-cms.com/display/DOCS62/Magnolia+6+UI+ports+of+5+UI+field+transformer+classes this will update - multi.MultiValueSubChildrenNodeTransformer row in the table now is supported using a configuration like:

  • use jcrMultiField with a field of $type: compositeField with a single property named the same way as the multifield is named. 

Example:

Comment by Viet Nguyen [ 23/Dec/20 ]

Basically this ticket does not need any code change or data change. Customers just need to configure using the new structure without the need of MultiValueChildrenNodeTransformer

To be clear, in case that customers already having data of MultiValueChildrenNodeTransformer, using our new configuration, Magnolia UI system can load and store data as usual.

The PR of MGNLCAT-187 showing an example of how to use this.
Example code:

relatedUUID:
          $type: jcrMultiField
          field:
            $type: compositeField
            properties:
              - name: relatedUUID
                $type: linkField
                datasource: *categoryDatasource
Comment by Viet Nguyen [ 12/Jan/21 ]

No response from customer so we are supposing things are going well there. We will consider opening a new one in case of customer come back for anything else. Thank you all for your support!

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