@nok-integration/storefront-react 0.19.10 → 0.19.15

package/dist/index.d.ts

@@ -2503,6 +2503,7 @@ declare function createClient(options: ClientOptions): {
                 cta: string;
                 image?: string | undefined;
                 target?: string | undefined;
+                video?: string | undefined;
                 focal_y?: number | undefined;
             }[];
         }>;
@@ -2858,6 +2859,7 @@ declare function createClient(options: ClientOptions): {
                     amount: number;
                     currency: string;
                 } | undefined;
+                returned_qty?: number | undefined;
             }[];
             totals: {
                 shipping: {
@@ -2951,6 +2953,7 @@ declare function createClient(options: ClientOptions): {
                     amount: number;
                     currency: string;
                 } | undefined;
+                returned_qty?: number | undefined;
             }[];
             totals: {
                 shipping: {
@@ -3729,6 +3732,20 @@ declare const OrderDetail: z.ZodObject<{
          */
         cancelled_qty: z.ZodNumber;
         refunded_qty: z.ZodNumber;
+        /**
+         * Units already reported as coming back.
+         *
+         * **The returns screen cannot compute what is left without it, and got it wrong.** The
+         * engine refuses a return of more than `qty - cancelled_qty - refunded_qty - returned_qty`
+         * (`returns.service`), and this was the only one of those four not on the wire — so a
+         * line returned in full still offered its full quantity, and choosing it answered 400
+         * `invalid_request` with "Only 0 of line_1 can be returned". Seen on UAT order 611887,
+         * 28 Aug.
+         *
+         * Optional so an engine that predates it stays valid; absent means zero, which is what a
+         * consumer already assumed.
+         */
+        returned_qty: z.ZodOptional<z.ZodNumber>;
     }, "strip", z.ZodTypeAny, {
         sku: string;
         qty: number;
@@ -3750,6 +3767,7 @@ declare const OrderDetail: z.ZodObject<{
         title?: string | undefined;
         image?: string | undefined;
         attributes?: Record<string, string> | undefined;
+        returned_qty?: number | undefined;
     }, {
         sku: string;
         qty: number;
@@ -3771,6 +3789,7 @@ declare const OrderDetail: z.ZodObject<{
         title?: string | undefined;
         image?: string | undefined;
         attributes?: Record<string, string> | undefined;
+        returned_qty?: number | undefined;
     }>, "many">;
     ship_to: z.ZodObject<{
         name: z.ZodString;
@@ -3951,6 +3970,7 @@ declare const OrderDetail: z.ZodObject<{
         title?: string | undefined;
         image?: string | undefined;
         attributes?: Record<string, string> | undefined;
+        returned_qty?: number | undefined;
     }[];
     totals: {
         shipping: {
@@ -4037,6 +4057,7 @@ declare const OrderDetail: z.ZodObject<{
         title?: string | undefined;
         image?: string | undefined;
         attributes?: Record<string, string> | undefined;
+        returned_qty?: number | undefined;
     }[];
     totals: {
         shipping: {
@@ -4241,20 +4262,27 @@ export declare interface OrderTimelineProps {
 }
 
 /**
- * Order tracking (Figma `order stats`, 5479:132209).
+ * Order tracking (Figma `order stats`, 5993:30258).
  *
  * One screen with three states, and the engine's `progress` is what draws them: the widget
  * says where the parcel is, and everything under it is the same for all three.
  *
  * The first state carries a "Cancel order" button and the last offers a return.
- * Cancelling happens in place, through the reason sheet; a return is three screens, so
- * "Return items" navigates to them. **Neither moves money** — both record a request and
- * hand it on, and nothing here computes or settles a refund.
+ * Cancelling happens in place, through the reason sheet; a return is three screens, and
+ * they open in place too unless the host has a route of its own. **Neither moves money** —
+ * both record a request and hand it on, and nothing here computes or settles a refund.
  *
  * Both are drawn on the ENGINE's say-so — `can_cancel` is its dispatch cut-off,
  * `can_return` its returns window. Neither is a status this screen can infer, and it does
  * not try.
  *
+ * **The return is offered in ONE place, and it is the "Start a return" row.** `order stats`
+ * draws no button under the timeline; the `Return flow` section's own entry frame
+ * (`5304:76852`) draws that button and no help block at all. The two disagree, and this
+ * screen belongs to `order stats` — the same rule that makes "Order placed" ignore the
+ * "Estimated delivery 22-27 Aug" headline that `Cancel flow` gives it. A screen that
+ * exists only inside a flow, like the cancelled state below, follows that flow's section.
+ *
  * "Contact support" is different again: the form behind it is DAZN's, but the row has
  * somewhere to go without them wiring anything, because pressing it raises
  * `support_requested`.
@@ -4270,15 +4298,14 @@ export declare interface OrderTrackingViewProps {
     /** Overrides the provider's locale for dates. */
     locale?: string;
     /**
-     * Open the return flow.
+     * Open the return flow on a route of your own.
      *
-     * Optional. The return flow is three SCREENS, and only the host knows where its routes
-     * are — the same reason `OrderListView` takes `onOpenOrder` rather than navigating
-     * itself. Mount `ReturnFlowView` with this order's reference and the whole flow is
-     * there.
+     * Optional. Pass it and you own the trip: point it at `<ReturnFlowView>` with this
+     * order's reference. Omit it and the flow opens in place on this screen, the way
+     * cancelling opens its reason sheet.
      *
-     * Without it the control is not drawn. The SDK will not offer a button whose destination
-     * does not exist, and that has not changed either.
+     * Either way the control is drawn whenever the engine sends `can_return`, so the frame's
+     * "Start a return" row is there for a fan whether you route it or not.
      */
     onStartReturn?: () => void;
     /**
@@ -5763,6 +5790,51 @@ export declare interface ShopSurfaceProps extends Omit<ComponentPropsWithoutRef<
 
 export declare type ShopTone = 'dark' | 'light';
 
+/**
+ * Full-bleed background video: muted, looping, inline, and never showing a control.
+ *
+ * The four attributes below are not stylistic. `muted` and `playsInline` together are the
+ * only combination iOS will start without a gesture — a video that is unmuted, or that is
+ * allowed to go fullscreen, simply does not play, and the panel shows its poster forever.
+ * `loop` is the brief. `controls` is absent because this is artwork behind copy, not a
+ * player: a tap belongs to the CTA stretched over the panel, and a play button in the
+ * middle of a category slide would sit directly on that hit area.
+ *
+ * **Playback follows visibility.** The shop entry is five full-screen panels, so a naive
+ * page decodes five simultaneous streams for four panels nobody is looking at. Each clip
+ * starts when its panel comes into view and pauses when it leaves, which keeps one video
+ * decoding at a time. Fetching is deferred the same way: `preload="none"` until the
+ * observer fires, so a fan who never scrolls past the hero pays for the hero alone.
+ *
+ * **Reduced motion is honoured by not playing at all.** Autoplaying background video is
+ * exactly what the preference is about, and there is a good still to fall back to — the
+ * poster is frame 0 of the clip, so the panel is the design's own opening frame rather
+ * than an empty box. The preference is read live rather than once: a fan can change it
+ * while the page is open, and on iOS it changes with the low-power setting.
+ */
+export declare function ShopVideo({ src, poster, fill, className, style, priority, }: ShopVideoProps): JSX.Element;
+
+export declare interface ShopVideoProps {
+    src: string;
+    /**
+     * Still shown until the first frame decodes, and the only thing shown when motion is
+     * reduced. Cut from frame 0 of `src` so there is no jump when playback starts.
+     */
+    poster?: string;
+    /**
+     * Fill the positioned ancestor, as `ShopImage`'s `fill` does. The parent must be
+     * `position: relative` (or absolute/fixed) — same requirement, same reason.
+     */
+    fill?: boolean;
+    className?: string;
+    style?: CSSProperties;
+    /**
+     * Above the fold. Fetches the file immediately instead of waiting for the panel to come
+     * into view. One video per screen should carry this; the rest should not.
+     */
+    priority?: boolean;
+}
+
 /**
  * Sizing help, shown in the PDP "Size guide" overlay (Figma `size-guide`, 4882:58365).
  *
@@ -5889,7 +5961,7 @@ export declare function sizeOptions(variants: ProductVariant[], colour?: string
  * choice the parent flips `error` and the message + scroll target appear (buttons stay
  * enabled per the design note). Chips are a real radiogroup for keyboard + SR support.
  */
-export declare function SizeSelector({ sizes, selected, onSelect, error, guide, }: SizeSelectorProps): JSX.Element;
+export declare function SizeSelector({ sizes, selected, onSelect, error, lowStock, guide, }: SizeSelectorProps): JSX.Element;
 
 export declare interface SizeSelectorProps {
     sizes: SizeOption[];
@@ -5898,6 +5970,14 @@ export declare interface SizeSelectorProps {
     onSelect: (value: string) => void;
     /** Show the "select a size" error (set after Add-to-cart is tapped with no selection). */
     error?: boolean;
+    /**
+     * "Only 1 left in M size", when the selected size is nearly gone.
+     *
+     * Rendered here rather than by the caller because the frame's `low-stock` layer lives
+     * INSIDE `mobile/pdp/size`, in the same slot as the error above it — the count is per
+     * size, so it belongs under the squares it is about.
+     */
+    lowStock?: string;
     /**
      * Category-wide sizing help. Absent = the control is not rendered at all, rather than
      * opening an empty overlay — until DAZN supplies a measurement chart most categories