Page History

...

* You can also use custom definition classes which will usually extend the classes mentioned above. In this case you have to provide the class as an attribute in the YAML file.

Deprecating a YAML-based definition

The introduction of the info.magnolia.config.source.yaml.construct.WrapMetadata construct in Magnolia 5.6.2 allows to deprecate YAML-based definitions. You can mark a YAML-based definition as deprecated like this:

deprecated: !metadata
  since: 5.5.6
  description: The dialog uses the deprecated PlaceholderTextFieldDefinition. Please use the placeholder property instead.

The deprecated definition is displayed in the Definitions app. Currently, the app reports the following deprecated (or non-existing) items:

• Deprecated classes used by any definition.
• Deprecated or non-existing templates used by block definitions.
• Template references.
  • Deprecated or non-existing dialogs
  • Deprecated or non-existing component definitions used in page definitions.
  • Non-existing template script paths.
  • Configured but non-existing renderer.

Reusing configuration in YAML files with !inherit and !include

...