ebc2471c6b
Prettier formatting our markdown files is causing bugs because of the differences between Gatsby's parser and Prettier's. Also, Prettier formats the inline code-blocks containing example CMS configs, but the formatting it uses doesn't really make much sense or match the suggested CMS config style. It doesn't actually make much sense to format the docs anyway, since we use the CMS itself to edit/generate them.
35 lines
1.2 KiB
Markdown
35 lines
1.2 KiB
Markdown
---
|
|
label: "Object"
|
|
target: object
|
|
---
|
|
|
|
The object widget allows you to group multiple widgets together, nested under a single field. You can choose any widget as a child of an object widget—even other objects.
|
|
|
|
- **Name:** `object`
|
|
- **UI:** a field containing one or more child widgets
|
|
- **Data type:** list of child widget values
|
|
- **Options:**
|
|
- `default`: you can set defaults within each sub-field's configuration
|
|
- `fields`: (**required**) a nested list of widget fields to include in your widget
|
|
- **Example:**
|
|
```yaml
|
|
- label: "Profile"
|
|
name: "profile"
|
|
widget: "object"
|
|
fields:
|
|
- {label: "Public", name: "public", widget: "boolean", default: true}
|
|
- {label: "Name", name: "name", widget: "string"}
|
|
- label: "Birthdate"
|
|
name: "birthdate"
|
|
widget: "date"
|
|
default: ""
|
|
format: "MM/DD/YYYY"
|
|
- label: "Address"
|
|
name: "address"
|
|
widget: "object"
|
|
fields:
|
|
- {label: "Street Address", name: "street", widget: "string"}
|
|
- {label: "City", name: "city", widget: "string"}
|
|
- {label: "Postal Code", name: "post-code", widget: "string"}
|
|
```
|