@qite/tide-components 1.0.7 → 1.0.9

package/build/build-esm/src/booking-product/types.d.ts

@@ -21,6 +21,16 @@ export interface Settings {
      * to the Tide API is unchanged.
      */
     disableRooms?: boolean;
+    /**
+     * When true, the traveller may pick the same day as departure and return
+     * (a 0-night stay), e.g. 20/09 - 20/09. By default a second click on the
+     * departure day restarts the selection instead of closing the range, which
+     * stays the behaviour for products that always span at least one night.
+     *
+     * Only affects `searchType: 0`; with `searchType: 1` the return date is
+     * dictated by the available date pairs coming from the API.
+     */
+    allowSingleDayDateSelect?: boolean;
     /**
      * Icon name shown next to the price whenever a price is available.
      * Defaults to `'ui-bed'` for backwards compatibility. Customers booking

package/build/build-esm/src/search-results/components/itinerary/itinerary-utils.d.ts

@@ -7,6 +7,18 @@ export declare const numberOfNights: (segment: PackagingEntryLine) => number;
 /** Icon per service type, so every node on the itinerary reads at a glance. */
 export declare const getServiceTypeIcon: (serviceType?: number) => string;
 export declare const getServiceTypeBadgeModifier: (serviceType?: number) => string;
+/**
+ * How long a node takes, in the same shape the flight legs are written in — an hour count only
+ * once there is one, so a short drive reads as plain minutes.
+ */
+export declare const getTrajectNodeDuration: (node: PackagingTrajectNode) => string;
+/** Icon per way of travelling, where the route records one. */
+export declare const getTransportTypeIcon: (transportType?: number | null) => string | null;
 export declare const POI_TRAJECT_NODE_TYPE = 2;
+/**
+ * A point of interest is a place on the map rather than a service, so it gets a marker. Anything
+ * else goes by how it is travelled where the route says so — a leg on foot or by bike is sold as
+ * nothing, and its service type falls back to a transfer — and by what it is where it does not.
+ */
 export declare const getTrajectNodeIcon: (node: PackagingTrajectNode) => string;
 export declare const getTrajectNodeBadgeModifier: (node: PackagingTrajectNode) => string;

package/build/build-esm/src/search-results/hooks/use-bookable-entry.d.ts

@@ -0,0 +1,11 @@
+import { PackagingEntry } from '@qite/tide-client';
+/**
+ * The entry to send to the backend, as opposed to the one the page works with.
+ *
+ * They differ only for a traject: the page keeps the line guids the traject was rendered with,
+ * because that is what joins its nodes to its lines, while pricing and booking need the guids the
+ * searches cached their lines under. Anything else passes through untouched, so this can be used
+ * wherever the entry leaves the component without checking which flow is running.
+ */
+declare const useBookableEntry: () => PackagingEntry | null;
+export default useBookableEntry;

package/build/build-esm/src/search-results/store/search-results-slice.d.ts

@@ -45,6 +45,8 @@ export interface SearchResultsState {
     trajectDaySuggestions: Record<number, TrajectDaySuggestions>;
     trajectEditLineGuid: string | null;
     trajectActivitiesDayOrder: number | null;
+    trajectResolving: boolean;
+    trajectItineraryView: boolean;
 }
 export type TrajectNodeStatus = 'idle' | 'loading' | 'resolved' | 'unavailable';
 export interface TrajectNodeAvailability {
@@ -86,7 +88,7 @@ export declare const setResults: import("@reduxjs/toolkit").ActionCreatorWithPay
 }, "searchResults/setTrajectNodeAvailability">, setTrajectNodeSelection: import("@reduxjs/toolkit").ActionCreatorWithPayload<{
     lineGuid: string;
     code: string;
-}, "searchResults/setTrajectNodeSelection">, setTrajectFlightLoading: import("@reduxjs/toolkit").ActionCreatorWithPayload<string, "searchResults/setTrajectFlightLoading">, setTrajectFlightAvailability: import("@reduxjs/toolkit").ActionCreatorWithPayload<{
+}, "searchResults/setTrajectNodeSelection">, setTrajectResolving: import("@reduxjs/toolkit").ActionCreatorWithPayload<boolean, "searchResults/setTrajectResolving">, setTrajectItineraryView: import("@reduxjs/toolkit").ActionCreatorWithPayload<boolean, "searchResults/setTrajectItineraryView">, setTrajectFlightLoading: import("@reduxjs/toolkit").ActionCreatorWithPayload<string, "searchResults/setTrajectFlightLoading">, setTrajectFlightAvailability: import("@reduxjs/toolkit").ActionCreatorWithPayload<{
     lineGuid: string;
     results: PackagingFlightResponse[];
     selectedGuid: string | null;

package/build/build-esm/src/search-results/utils/traject-utils.d.ts

@@ -23,31 +23,49 @@ export interface TrajectSearchContext {
 }
 export declare const buildTrajectClientConfig: (context: SearchResultsConfiguration) => TideClientConfig;
 export declare const buildTrajectSearchContext: (context: SearchResultsConfiguration, trajectEntry: PackagingTrajectResponse) => TrajectSearchContext;
-export declare const buildTrajectNodeRequest: ({ node, line }: TrajectNodeWithLine, context: TrajectSearchContext, productCode: string) => PackagingAccommodationRequest;
+export declare const buildTrajectNodeRequest: ({ node, line }: TrajectNodeWithLine, context: TrajectSearchContext, productCode: string, destination?: PackagingDestination) => PackagingAccommodationRequest;
 export declare const getDayDestinationItem: (items: TrajectNodeWithLine[], dayOrder: number) => TrajectNodeWithLine | null;
 export declare const getDayDestination: (items: TrajectNodeWithLine[], availability: Record<string, {
     results: PackagingAccommodationResponse[];
     selectedCode: string | null;
 }>, dayOrder: number) => PackagingDestination | null;
 export declare const buildTrajectDayExcursionRequest: (date: string, destination: PackagingDestination, context: TrajectSearchContext) => PackagingAccommodationRequest;
-/**
- * Entry lines for an excursion the traveller picked out of the suggestions.
- *
- * A traject node already has its lines and only needs stamping; a suggestion has none, so this
- * builds them — one per selected option, as the regular day-by-day excursion flow does, since an
- * excursion's options are ticket types (adult, child) rather than rooms. Where the search marks no
- * default, the first option of each room stands in.
- */
+type ExcursionOption = PackagingAccommodationResponse['rooms'][number]['options'][number];
+export declare const getExcursionOptionGroups: (result: PackagingAccommodationResponse) => ExcursionOption[][];
+export declare const excursionNeedsChoice: (result: PackagingAccommodationResponse) => boolean;
 export declare const buildTrajectExcursionLines: (result: PackagingAccommodationResponse) => PackagingEntryLine[];
+export declare const buildExcursionSearchParams: (result: PackagingAccommodationResponse) => {
+    date: string;
+    fromDate: string;
+    toDate: string;
+    countryId: number | null | undefined;
+    regionId: number | null | undefined;
+    oordId: number | null | undefined;
+    locationId: number | null | undefined;
+    locationName: string;
+    accommodationCode: null;
+    accommodationName: null;
+    hotelCode: string;
+    hotelName: string;
+    rooms: import("@qite/tide-client").PackageMainRoom[];
+};
 export interface DayActivityCard {
     result: PackagingAccommodationResponse;
-    /** The traject node this result answers, where it is one of the trip's own excursions. */
     item?: TrajectNodeWithLine;
 }
 export declare const buildDayActivityCards: (items: TrajectNodeWithLine[], availability: Record<string, {
     results: PackagingAccommodationResponse[];
     selectedCode: string | null;
 }>, suggestions: PackagingAccommodationResponse[]) => DayActivityCard[];
+/**
+ * Where to search for a node.
+ *
+ * Normally the node says so itself, through the product it was configured with. An excursion slot
+ * left empty on the traject says nothing at all — no code, no alternatives, and a line with no
+ * place on it — so it falls back to wherever the party is staying that day, the same anchor the
+ * day's own activity search uses.
+ */
+export declare const getNodeSearchDestination: (items: TrajectNodeWithLine[], item: TrajectNodeWithLine) => PackagingDestination;
 export declare const getConfiguredExcursionCodes: (items: TrajectNodeWithLine[], dayOrder: number) => Set<string>;
 export declare const getNodeCandidates: (node: PackagingTrajectNode) => PackagingTrajectAlternative[];
 export declare const findCandidateForResult: (node: PackagingTrajectNode, result: PackagingAccommodationResponse) => PackagingTrajectAlternative | null;
@@ -57,6 +75,25 @@ export declare const pickCheapest: (results: PackagingAccommodationResponse[]) =
 export declare const applyResultToLines: (lines: PackagingEntryLine[], result: PackagingAccommodationResponse) => PackagingEntryLine[];
 export declare const applyResultToLine: (line: PackagingEntryLine, result: PackagingAccommodationResponse, roomIndex?: number) => PackagingEntryLine;
 export declare const buildTrajectFlightRequest: ({ node, line }: TrajectNodeWithLine, context: TrajectSearchContext, pax: FlightSearchRequest["pax"]) => FlightSearchRequest;
+/**
+ * The entry as the backend can price it.
+ *
+ * A search caches an EntryLine per option and hands back that line's guid on the option. The
+ * backend then rebuilds the entry by looking each line up in that cache on its guid, so a line
+ * it cannot find is dropped — PackagingEntryBuilder.SyncEntryLines skips it, and an entry whose
+ * lines all came off a traject prices as nothing at all.
+ *
+ * A traject entry is rendered before any search runs, so its lines carry the guids the traject
+ * mapper gave them. This swaps in the guid of whatever each line resolved onto, leaving the
+ * lines the traveller added themselves alone — those were built from a search result and already
+ * carry the right one.
+ */
+export declare const withCachedEntryLineGuids: (entry: PackagingEntry, trajectEntry: PackagingTrajectResponse, nodeAvailability: Record<string, {
+    results: PackagingAccommodationResponse[];
+    selectedCode: string | null;
+}>, flightAvailability: Record<string, {
+    selectedGuid: string | null;
+}>) => PackagingEntry;
 export declare const pickCheapestFlight: (flights: PackagingFlightResponse[]) => PackagingFlightResponse | null;
 export declare const applyFlightToLine: (line: PackagingEntryLine, flight: PackagingFlightResponse) => PackagingEntryLine;
 /**
@@ -66,3 +103,4 @@ export declare const applyFlightToLine: (line: PackagingEntryLine, flight: Packa
  */
 export declare const isExternalResult: (result: PackagingAccommodationResponse) => boolean;
 export declare const isExternalCandidate: (candidate: PackagingTrajectAlternative) => boolean;
+export {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qite/tide-components",
-  "version": "1.0.7",
+  "version": "1.0.9",
   "description": "React components for Tide (booking, product availability, form, ...)",
   "main": "build/build-cjs/index.js",
   "types": "build/build-cjs/src/index.d.ts",
@@ -36,7 +36,7 @@
   "devDependencies": {
     "@jsonurl/jsonurl": "^1.1.4",
     "@popperjs/core": "^2.10.2",
-    "@qite/tide-client": "^2.0.16",
+    "@qite/tide-client": "^2.0.17",
     "@reduxjs/toolkit": "^2.8.2",
     "@rollup/plugin-commonjs": "^19.0.1",
     "@rollup/plugin-json": "^4.1.0",

package/styles/components/_search.scss

@@ -371,12 +371,12 @@
       display: flex;
       flex-direction: column;
       justify-content: center;
+      gap: 10px;
 
       height: 173.5px;
       padding: 0 20px;
 
       &__wrapper {
-        padding: 20px 0px;
         display: flex;
         flex-direction: column;
         align-items: center;
@@ -949,6 +949,25 @@
           border: var(--tide-booking-search-results-label-date-border--secondary);
         }
       }
+
+      // Something inside a day rather than a day of its own: no date, no box, and quieter type,
+      // sitting close to what it introduces.
+      &--sub {
+        grid-template-columns: 1fr;
+        grid-template-rows: auto;
+        margin-top: 20px;
+
+        .search__results__label__text {
+          height: auto;
+          border: none;
+          padding: 0px;
+          gap: 8px;
+
+          h3 {
+            font-size: 16px;
+          }
+        }
+      }
     }
 
     &__options {