Scheduling infrastructure for absolutely everyone.
docs: clarify bookingFields replacement behavior in update event type input (#22554)
devin-ai-integration[bot]969b58f17d9b
diff --git a/packages/platform/types/event-types/event-types_2024_06_14/inputs/update-event-type.input.ts b/packages/platform/types/event-types/event-types_2024_06_14/inputs/update-event-type.input.tsindex b281fe5d15c..51fe0476641 100644--- a/packages/platform/types/event-types/event-types_2024_06_14/inputs/update-event-type.input.ts+++ b/packages/platform/types/event-types/event-types_2024_06_14/inputs/update-event-type.input.ts@@ -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) },