[MAGNOLIA-7127] Order of field are not according to definition when using !include: directive Created: 31/Aug/17 Updated: 31/Aug/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | gui |
| Affects Version/s: | 5.5.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Jordie Diepeveen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
| Description |
|
Since magnolia 5.5.6, using the new !include: directive, the fields are not in the correct order anymore.
form:
tabs:
- name: pageMain
fields: !include:/tte/includes/fields/homePageTabMainFields.yaml
Will result in an incorrect order of the field being included
form:
tabs:
- name: pageMain
fields: !include /tte/includes/fields/homePageTabMainFields.yaml
Will result in the correct order of the field being included |