@timum/booking 1.5.4 → 1.5.6

package/README.md

@@ -289,6 +289,17 @@ This object's options directly affect timum's behaviour or allow you to react to
       </ul>
       </blockquote>   
       </td>
+   </tr>
+      <tr>
+      <td>prdRefs</td>
+      <td>string/array, Reference(s) of specific products. For when you only want your customer to choose from a subset of your otherwise fully available list of active products.
+      <blockquote>
+        Note: If this and <code>tslRefs</code> are defined in conjunction: 
+        To facilitate a seamless booking process, all products linked to appointments or availabilities are made selectable for customers. This ensures that customers can always choose a product that grants access to the corresponding bookable timeslots referenced in <code>tslRefs</code>.
+        Without this step, customers might be restricted by <code>prdRefs</code> from selecting certain products, rendering related appointments or availabilities unselectable. In this way, <code>tslRefs</code> has priority over this field.
+</blockquote>  
+ </td>
+
    </tr>
    <tr>
       <td>platform</td>
@@ -383,6 +394,8 @@ The callbacks object may contain any of the following functions.
 
 ##### Booking related
 
+- `openedBookingPage`
+- `closedBookingPage`,
 - `createBookingStarted`
 - `createBookingSuccessfull`
 - `createBookingFailed`
@@ -426,6 +439,8 @@ Additionally, `createBookingFailed` and `createBookingSuccessfull` also have a R
 
 ##### Cancelation Related
 
+- `openedCancelPage`
+- `closedCancelPage`
 - `cancelationStarted`
 - `cancelationSuccessful`
 - `cancelationFailed`
@@ -434,6 +449,21 @@ All cancelation related callbacks receive a single obejct as argument containing
 
 Additionally, `cancelationSuccessful` and `cancelationFailed` also have a RTKQ response object in their respecive argument. See here for a reference.
 
+<a name=”dialog_related”></a>
+
+##### Dialog related
+
+In addition to the dialog related callbacks already mentioned in [Cancelation Related](#cancelation_related) and [Booking related](#booking_related), there a callbacks for all other dialogs as well.
+
+- `openedProductSelection`
+- `openedResourceSelection`
+- `openedConfirmationPage`
+- `closedProductSelection`
+- `closedResourceSelection`
+- `closedConfirmationPage`
+
+These do not receive any parameters.
+
 <a name=”data_fetching_related”></a>
 
 ##### Data Fetching Related
@@ -713,10 +743,10 @@ Anatomy of a custom booking form field:
 
 ```
   <fieldName> : {
-      index: number, index defines the order in which the fields get displayed. 
-                     (If you want to reorder the default fields or 
-                      want to inject a custom field between them, 
-                      you must redefine them as custom fields and manually change their indexes.) 
+      index: number, index defines the order in which the fields get displayed.
+                     (If you want to reorder the default fields or
+                      want to inject a custom field between them,
+                      you must redefine them as custom fields and manually change their indexes.)
       title: string or JSXElement;
       validation: yup based validation. See https://github.com/jquense/yup. Re-exported and accessible via timum.yup
       type: string; either 'text' (default), 'phoneNumber', 'textarea', 'checkbox' or 'select',

package/build/booking.js

@@ -1,4 +1,4 @@
-import { R as s, I as t, K as e, G as n, H as o, J as m } from "./index-876ec840.js";
+import { R as s, I as t, K as e, G as n, H as o, J as m } from "./index-96e7cb25.js";
 export {
   s as React,
   t as TimumBooking,