|Description||Object field for containing other fields|
|Base Field Type||container|
|maxProperties||number||The maximum number of properties that this object is allowed to have|
|minProperties||number||The minimum number of properties that this object is required to have|
|properties||object||List of child properties.|
|animate||boolean||true||Up and down transitions will be animated|
|collapsed||boolean||Field set is initially collapsed if true.|
|collapsible||boolean||Field set is collapsible if true.|
|lazyLoading||boolean||Child fields will only be rendered when the fieldset is expanded if this option is set true.|
|legendStyle||string||button||Field set legend style.|
|order||number||Allows for optional specification of the index of this field in the properties array.|
A simple object field. If you give Alpaca an object as it's data, it automatically figures out what to do and sets up both sub-fields for you.
Here we provide a schema to go along with our data. The schema simply provides a bit more information about the two sub-fields, such as their type and labels.
Here is a more complex example that provides the data, schema and options for all of the sub-fields of the object.
Object field with schema, options and view parameter.
Object field with default value.
Object field with lazy loading option. The lazy loading option is useful for improving performance of rendering forms for large schemas.
Object field rendered in display-only mode. The
gender field is hidden.
Object with a required field specified at the field level.
Object with a required field specified at the object-level.
Object that utilizes field-level
order property to apply an order to child fields.
Here is an example of an object field where we use a top-level layout and a nested override of the view to force the email address into display mode only.