Details
-
Improvement
-
Resolution: Workaround exists
-
Neutral
-
None
-
5.5.6
-
None
-
None
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)
Checklists
Acceptance criteria