@wix/auto_sdk_bookings_bookings 1.0.58 → 1.0.59

package/build/internal/es/index.typings.d.mts

@@ -3807,7 +3807,7 @@ declare function onBookingUpdated(handler: (event: BookingUpdatedEnvelope) => vo
  * on the `paymentStatus` you provide, double booking conflicts, and whether
  * the service requires business approval.
  *
- * ## eCommerce checkout restriction
+ * ### eCommerce checkout restriction
  *
  * Call this method only when using a custom checkout page. Don't
  * call it when using a *Wix eCommerce checkout*
@@ -3816,7 +3816,7 @@ declare function onBookingUpdated(handler: (event: BookingUpdatedEnvelope) => vo
  * the `paymentStatus` of the corresponding *Wix eCommerce order*
  * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)).
  *
- * ## New booking status
+ * ### New booking status
  *
  * The booking `status` is set to `DECLINED` if both of the following conditions
  * are met:
@@ -3826,13 +3826,13 @@ declare function onBookingUpdated(handler: (event: BookingUpdatedEnvelope) => vo
  * If only one or none of these conditions is met, `status` is set to `PENDING`
  * or `CONFIRMED` depending on whether the service requires business approval.
  *
- * ## Double bookings
+ * ### Double bookings
  *
  * If there is a double booking conflict, but the booking has already been at least
  * partially paid, the method still marks the booking as `PENDING` or `CONFIRMED`.
  * Then, it also sets `doubleBooked` to `true`.
  *
- * ## Admin overwrites
+ * ### Admin overwrites
  *
  * There are small but important differences in confirmation behavior if the
  * booking was created with special `flowControlSettings`: