[MAGNOLIA-7065] Inheritance of registry definitions from JCR Created: 12/Jun/17 Updated: 15/Jun/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| 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)
|
||||||||||||
| Story Points: | 21 | ||||||||||||
| Description |
|
Implement the feature described in https://jira.magnolia-cms.com/browse/MAGNOLIA-6664, but definable in JCR configuration. Summarized: When creating a definition in JCR - it is possible to use an "inherits" feature such that the current definition starts with all properties of the inherited definition, but can then override those values with new ones. The "inherits" feature is similar to "extends", except that with "inherits" you refer to a definition in the registry (no matter what source created the definition), and that it is only possible to inherit a complete definition. (not a sub part of a definition.) |