[MAGNOLIA-7182] Control yaml inheritance dependencies within a single light module Created: 17/Oct/17 Updated: 12/Mar/19 Resolved: 12/Mar/19 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.5.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jonathan Ayala | Assignee: | Unassigned |
| Resolution: | Workaround exists | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| 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)
|
||||
| Description |
|
When inheriting yaml configuration among components inside a single module, order of loading seems not to take inheritance into consideration and, as a consequence, a missing definition dependency error occurs. That can be fixed by modifying any of those yaml files (without any change, simply saving it) but as an improvement, it would be good if Magnolia checked those dependencies at file level just as it is done at module-level during first loading. There is a linked support ticket where this matter has been reported including a light module in which the above mentioned situation can be reproduced. (Attached screenshot from the module's error) |
| Comments |
| Comment by Jonathan Ayala [ 12/Mar/19 ] |
|
According to docs we shouldn't inherit from components within same module, therefore it isn't a good practice and must be avoided. |