Skip to content

Commit 85f75fa

Browse files
Revert "docs(scheduler): resource fields are mandatory"
This reverts commit a15d992.
1 parent 7994103 commit 85f75fa

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

components/scheduler/resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ To use resources:
3838
* Set its `Field` parameter to a string that will point to the name of the field in the appointment that associated appointments with the resource type.
3939
* The `Title` parameter defines the text shown for its dropdown in the [edit form]({%slug scheduler-appointments-edit%}).
4040
1. Provide a collection of resource entries for each type of resource you will use to the `Data` parameter of the resource.
41-
* The `ColorField`, `ValueField` and `TextField` let you specify fields in the resource model that contain the data. These fields must all be of type `string`. The default values are `Value`, `Text`, `Color` respectively. Each resource entry must have values in all three fields.
41+
* The `ColorField`, `ValueField` and `TextField` let you specify fields in the resource model that contain the data. These fields must all be of type `string`. The default values are `Value`, `Text`, `Color` respectively.
4242
1. Define appointments [as usual]({%slug scheduler-appointments-databinding%}). Add a `string` field to them for each resources type they will require. The name of this field must match the value of the `Field` parameter of the resource declaration.
4343
* If you are using multiple resource types, you will need a field for each resource.
4444
1. Populate the appointment field that matches the resource name with the corresponding `Value` of the resource that you want associated with it.

0 commit comments

Comments
 (0)