_Common complex field properties

`name`	required Name of the field definition item. Derived from the configured node name. Use alphanumeric characters without spaces.
`class`	required (unless `$type` is used) Type of the field definition item. The value must be a fully qualified class name and a subtype of `info.magnolia.ui.field.FieldDefinition`. See Field types for possible values.
`$type`	You can use this as a shortcut for `class` if the definition class is annotated with `info.magnolia.ui.field.FieldType`. The proper value is defined by the annotation. Example class annotation Expand source @FieldType("textField") public class TextFieldDefinition extends ConfiguredFieldDefinition<String> { ... } To use the `$type` property in YAML, see Example field definition.
`itemProvider`	required (used only in composite, multi and switchable fields) Node with a `$type` property that specifies the type of data binding for the subnodes in complex fields. See Item providers for more information.
`description`	optional Help text displayed when the user clicks the help icon. The value can be literal or a key of a message bundle.
`i18n`	optional, default is `false` Enables i18n authoring support, which allows editors to write foreign-language or regionally targeted content. A two-letter language identifier (`en`, `de`, `fr`, etc.) is displayed on controls where `i18n` is set to `true`.
`label`	optional Field label displayed to editors. The value can be literal or a key of a message bundle. If you do not provide the property, Magnolia will fall back to a generated i18n key. If you do not want a label at all, define the property and set its value to a blank space such as `label: " "` in YAML.
`styleName`	optional Additional style information for an editor property definition item applied to the element when the form is rendered. The value can be a CSS class or a list of CSS classes separated by white spaces.

Page tree

_Common complex field properties