[MAGNOLIA-6669] Remove node via YAML decoration Created: 18/May/16 Updated: 30/Oct/17 Resolved: 30/Oct/17 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.4.6 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 2 |
| Labels: | arch-review | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
||||
| Epic Link: | LD: Fundamental features | ||||
| Description |
|
It should be possible to remove a node with the YAML decoration feature. Reason: For example, it is not currently possible to remove a field or tab from a dialog, or remove a page or a component from an availability. Allowing to remove and re-add a node (override) would also enable removing specific properties which is not currently possible, but should eventually be supported. See docs describing the current limitation: https://documentation.magnolia-cms.com/display/DOCS/Definition+Decoration#Definitiondecoration-Overridingpropertiesandchangingsubitems To Specify: The syntax could use the concept of an override borrowed from JCR extends mechanism which removes all of the properties and subnodes of a node. Validation: https://wiki.magnolia-cms.com/display/PMTEAM/Decoration+improvements+LDV |
| Comments |
| Comment by Christopher Zimmermann [ 22/Nov/16 ] |
|
Note - Goal: the syntax should be the same for extends as for decoration. TODO:
|
| Comment by Christopher Zimmermann [ 19/Dec/16 ] |
|
There was some concern about adding this feature, and examples where this would be necessary were requested. Decoration is useful in both light modules and maven modules. It enables modules to change the configuration brought in by other modules. - in a non-destructive way that is automatically removed when the module is removed. Examples:
Modify an app.
I am preparing a demo based on the travel demo. (Or based on another existing demo or templating kit.)
|
| Comment by Christopher Zimmermann [ 26/Jan/17 ] |
|
Removing from backlog based on concerns from PD. |
| Comment by Christopher Zimmermann [ 30/Oct/17 ] |
|
5.5.6 Introduced the ability to use an "!override" feature in YAML. To be consistant it is also available in decorations. |