[MGNLUI-5625] Harmonize nodeType configuration for definitions Created: 24/Jan/20 Updated: 25/Feb/20 Resolved: 30/Jan/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Rishab Dhar | Assignee: | Rishab Dhar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
Background: While fixing the issue nodeTypes: - name: mgnl:page - name: mgnl:variants It was further noted that other nodeType configurations in personalization-pages/decorations/pages-app/apps/pages-app.yaml were of the form of List of NodeType objects. As a consequence, there are two things that need to be analyzed and fixed:
|
| Comments |
| Comment by Rishab Dhar [ 29/Jan/20 ] |
|
After further analysis with mgeljic it was found the source of the bug is due to incorrect translation of yaml properties defined using Maps into string values via their toString() methods to populate a collection. |
| Comment by Rishab Dhar [ 30/Jan/20 ] |
|
Some important points regarding changes made:
Regarding personalization module - all nodeType properties have been updated in pages-app.yaml as a list of Strings to maintain consistency. |