[YAMLEXT-6] merge !override and !exclude Created: 01/Dec/16 Updated: 16/Mar/23 Resolved: 16/Mar/23 |
|
| Status: | Closed |
| Project: | Yaml extensions (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Matthias Müller | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
The yaml tags !override and !exclude seem to do exactly the same, except that !override requires some properties/subnodes and throws some cryptic (not even the filename, which caused the error, is logged) error message, if there are no properties/subnodes. I suggest, that !exclude is removed and !override is adapted, so it doesn't require any properties/subnodes to be set and therefore behaves exactly like jcr's extends:override, which developers are used to. e.g. the following should work default.yaml someNode: someProp: true someOtherNode: someOtherProp: true adapted.yaml !extend:/default.yaml someOtherNode: !override expected result of adapted.yaml: someNode: someProp: true |
| Comments |
| Comment by Daniel Kasmeroglu [ 20/Dec/17 ] |
| Comment by Adam Jones [ 16/Mar/23 ] |
|
Closing due to project being archived. |