[MAGNOLIA-7126] Fields defined in a YAML list get re-ordered when included with new !include:/path.yaml syntax Created: 30/Aug/17  Updated: 21/Nov/17  Resolved: 27/Oct/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5.8, 5.6

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive walkthrough.zip    
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
Epic Link: LD: Fundamental features
Sprint: Basel 119
Story Points: 3

 Description   

I'm using !include to include a YAML file with a tab definition which includes a YAML list of fields.

When I use the old !include[space] syntax, the field order remains the same.
When I use the new !include: syntax, the field order is rearranged.

The field order should not change.

To reproduce:

  • load light module attached as a zip.
  • In page editor, create a page with walkthrough template.
  • Add a "c" component to the page.
  • Try changing the which include syntax is used in the /walkthrough/dialogs/components/c.yaml file.

Note that if the YAML snippet with the list of fields is defined as a map instead of a yaml list, then the fields do not get re-ordered. (You can use the myCoolTabMap.yaml file to test this)


Generated at Mon Feb 12 04:20:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.