[MAGNOLIA-6664] Inheritance of registry definitions from YAML Created: 12/May/16 Updated: 31/Jan/18 Resolved: 20/Jul/17 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.5.6, 5.6 |
| Type: | Story | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | None | ||
| 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)
|
||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Epic Link: | LD: Fundamental features | ||||||||||||||||||||||||||||||||||||
| Sprint: | Basel 103, Basel 104, Basel 105 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||||||||||||||
| Description |
|
Introduce "inherits" for inheriting a definition from a registry.
|
| Comments |
| Comment by Christopher Zimmermann [ 22/Nov/16 ] |
|
TODO:
Note: ticket is blocked because of above linked ticket. |
| Comment by Antti Hietala [ 02/Feb/17 ] |
|
Next step:
|
| Comment by Mikaël Geljić [ 17/Mar/17 ] |
|
Hey jsimak, please take a look at Please reopen if you can reproduce it. Unless you made major changes, there's little chance to escape |
| Comment by Roman Kovařík [ 27/Mar/17 ] |
|
Reopened:
|
| Comment by Michael Mühlebach [ 20/Apr/17 ] |
|
Should not be decided just by PM. Please have a consent between PM, Dev and Services. |
| Comment by Christopher Zimmermann [ 08/Jun/17 ] |
|
Conclusions after meetings with PM & PD: Continue to support "extends" for JCR without any change. Introduce "inherits" for inheriting a definition from a registry.
Related - but to implement in another ticket: Enhance "include" for YAML.
We do not introduce any ability to cross "extend" between jcr, yaml, and code sources besides the new "inherits" feature. |
| Comment by Christopher Zimmermann [ 12/Jun/17 ] |
|
After discussion with Philip, decided to split ticket. Implementation for JCR: https://jira.magnolia-cms.com/browse/MAGNOLIA-7065 |
| Comment by Christopher Zimmermann [ 12/Jun/17 ] |
|
Unassigning so that the work is not blocked. |