Registry data source
The registry data source supplies a list of definition providers of a given registry specified by the registry type. It’s only used in filters in the Definitions app. By default, it doesn’t provide any component implementation itself other than the one required by select fields.
|
The registry data source is part of the Magnolia 6 UI framework. The
fully qualified class name is
If you work with the Magnolia 5 UI framework, see Content connector instead. |
Example definition
datasource:
class: info.magnolia.definitions.app.data.RegistryDatasourceDefinition
name: registry-contents
type: dialogsList of properties
| Property | Description |
|---|---|
|
required Fully qualified name of the definition class. Use |
|
required Type of registry. Examples include |
|
optional, default is Name of the data source. |
Data source components
Module component mappings can be defined in the context of the current
data source (a component section should have an id in the form of
<id>datasource-<ds-name></id>, where <ds-name> is configured in the
definition).
| Type | Implementation | Description |
|---|---|---|
|
|
Provides delegates required by select fields. |
<components>
<id>datasource-registry-contents</id>
<component>
<type>info.magnolia.ui.field.SelectFieldSupport</type>
<implementation>info.magnolia.definitions.app.data.RegistryContentSelectFieldSupport</implementation>
</component>
</components>