@timum/booking 1.5.0 → 1.5.2

package/README.md

@@ -259,9 +259,37 @@ This object's options directly affect timum's behaviour or allow you to react to
    </tr>
    <tr>
       <td>ref</td>
-      <td>string/array, Reference of the resource to show the appointments of. <br><em> This is the only prop that is mandatory.</em><br> Everything else is optional. <br>Can also be a url parameter.
+      <td>string/array, Reference of the resource to show the appointments of. <br><em> Either this or tslRefs (see below) must be defined.</em><br> Everything else is optional. <br>Can also be a url parameter.
       <br>You can also provide a list of string references. Booking.js will then allow your customer to choose for which resource appointments should be displayed.</td>
    </tr>
+   <tr>
+      <td>tslRefs</td>
+      <td>string/array, Reference(s) of specific appointments. For when you only want to share a selection of a resource's appointments.<br><em>Either this or refs (see above) must be defined.</em><br> Everything else is optional. <br>Can also be a url parameter.
+      <br>You can also provide a list of string references. Booking.js will then load all appointments and corresponding resource information. If they belong to different resources, then bookingjs allows your customer to choose for which resource appointments should be displayed.
+      <blockquote>
+      Note: If this and ref are defined in conjunction: 
+      The following behaviour is not yet set in stone and may<b> change in the future. </b><br>
+      First, bookingjs will load all appointments of the given resources. It then loads all the appointments defined in tslRefs. It then tries to match both results in the following way:<br><br>
+      If a ref has none of it's appointments referenced in tslRef: <br>
+      <ul>
+        <li>allow the corresponding resource to be selected by the customer.</li> 
+        <li>show all free and bookable appointments of that resource.</li>
+      </ul> 
+      <br>
+      If a tslRef belongs to a resource also defined in ref:
+      <ul>
+        <li>allow the corresponding resource to be selected by the customer.</li> 
+        <li>show only the appointments defined in tslRefs. Discard all other appointments which would have otherwise been bookable.</li>
+      </ul> 
+      <br>
+      If a tslRef belongs to no resource defined in ref:
+      <ul>
+        <li>allow the corresponding resource to be selected by the customer.</li> 
+        <li>show (and load) only the corresponding appointment.</li>
+      </ul>
+      </blockquote>   
+      </td>
+   </tr>
    <tr>
       <td>platform</td>
       <td>string, A fully qualified reference (<code>id@someUuid@platform</code>) can be unwieldy especially if used as a url param. This prop allows you to hardcode the <code>platform</code> part.
@@ -338,7 +366,7 @@ This object's options directly affect timum's behaviour or allow you to react to
    </tr>
    <tr>
       <td>localization</td>
-      <td>object. Contains all localization variables and their standard texts. timum nativly supports English and German. Use this to override the standard text and/or add translations for your custom field labels and input validations (see the localisation guide for mor info.)
+      <td>object. Contains all localization variables and their standard texts. timum nativly supports English, German, French, Spanish and Italian. Use this to override the standard text and/or add translations for e.g your custom field labels and input validations (see the localisation guide for more info.)
       <br>
       Needs professional plan. 
       </td>
@@ -666,6 +694,10 @@ The standard configuration can be overridden except for the aforementioned field
           (value) => value === true
         ),
     },
+    locale: {
+      index: 6,
+      preventRendering: true,
+    },
   },
 ```
 
@@ -681,11 +713,15 @@ 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.) 
       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',
-      prefilled: string; value a fiels is initiated with.
-                 Note that for fields of type 'select' you must use the 'key' of on of it's options.
+      prefilled: string; value a field is initiated with.
+                 Note that for fields of type 'select' you must use the 'key' of one of it's options.
       preventRendering: boolean, default false;
                         if true the field is not visible to the user.
                         Useful in conjunction with sendCustomValuesInMessage allowing you to

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-58c1500e.js";
+import { R as s, I as t, K as e, G as n, H as o, J as m } from "./index-63dd2af1.js";
 export {
   s as React,
   t as TimumBooking,