[YAMLEXT-9] Is there a way to "inherit" availableComponents in an area definition Created: 21/Feb/17 Updated: 19/Jul/17 Resolved: 20/Mar/17 |
|
| Status: | Closed |
| Project: | Yaml extensions (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Support Request | Priority: | Neutral |
| Reporter: | Fadi Wissa | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MGNL 5.4.7 |
||
| Issue Links: |
|
||||
| Template: |
|
||||
| Documentation update required: |
Yes
|
||||
| Description |
|
We have recently switched to using YAML configuration and have the current pain point: Area A has availableComponents: a1, a2, a3 Area AB needs to have availableComponents: a1, a2, a3 and b1, b2, b3 (needs to merge availability from A with those from B) I have been able to use the !include as follows:
However, if any component needs to add even a single additional component (or merge two lists) I have not managed to make the !include work multiple times (to merge) and have not been able to add other components after the !include was used (to extend) ... so I had to copy and paste the list of components and add/modify as needed I would appreciate your feedback if there's a way around this. |
| Comments |
| Comment by Fadi Wissa [ 22/Feb/17 ] |
|
Never mind this one - I just used the !extend tag from this solution: Thank you! |