-
Story
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Basel 103, Basel 104, Basel 105
-
2
Introduce "inherits" for inheriting a definition from a registry.
- Ability to override values by supplying them under the !inherits statement. (As proposed in the light-yaml forge module with the "extends-def" keyword.)
- Supports override keyword to stop the extending.
- Do not allow inheriting from a sub definition. (ie don't support the ":/form" at the end of !inherits:dialogs:mtk:components/image:/form)
- Referencing syntax starts with the type name. In the referencing syntax, types do have an s at the end - ie "dialogs".
- Implement for YAML - (it will also be implemented for JCR and code (think blossom) in other tickets
- Log error message in case someone puts the typename after the module-name or makes some other anticipated mistake.
- depends upon
-
MGNLUI-3882 Reference fields by name as well as by fully qualified classname
- Closed
- is related to
-
MAGNOLIA-7115 Parsing of yaml fragment attempts to mutate immutable map
- Closed
- relates to
-
MAGNOLIA-6729 Stale session on accessing JCR resources
- Closed
-
MGNLUI-4256 App launcher layout update should be conducted in a thread safe manner and with MgnlContext provided
- Accepted
-
MAGNOLIA-7065 Inheritance of registry definitions from JCR
- Open
-
MAGNOLIA-7060 Override properties in YAML include
- Closed