docs: clarify bookingFields replacement behavior in update event type input (#22554)
* docs: clarify bookingFields replacement behavior in update event type input Update description to explain that bookingFields array completely replaces existing fields rather than adding to them. Users must fetch existing fields first before making modifications. Co-Authored-By: lauris@cal.com <lauris@cal.com> * Update update-event-type.input.ts --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: lauris@cal.com <lauris@cal.com> Co-authored-by: Lauris Skraucis <lauris.skraucis@gmail.com>
This commit is contained in:
co-authored by
lauris@cal.com <lauris@cal.com>
Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
lauris@cal.com <lauris@cal.com>
Lauris Skraucis
parent
a0e25ff270
commit
969b58f17d
+1
-1
@@ -159,7 +159,7 @@ class BaseUpdateEventTypeInput {
|
||||
@ValidateInputBookingFields_2024_06_14()
|
||||
@DocsPropertyOptional({
|
||||
description:
|
||||
"Custom fields that can be added to the booking form when the event is booked by someone. By default booking form has name and email field.",
|
||||
"Complete set of booking form fields. This array replaces all existing booking fields. To modify existing fields, first fetch the current event type, then include all desired fields in this array. Sending only one field will remove all other custom fields, keeping only default fields plus the provided one.",
|
||||
oneOf: [
|
||||
{ $ref: getSchemaPath(NameDefaultFieldInput_2024_06_14) },
|
||||
{ $ref: getSchemaPath(EmailDefaultFieldInput_2024_06_14) },
|
||||
|
||||
Reference in New Issue
Block a user