@akinon/pz-theme 2.0.95-beta.1 → 2.0.95-rc.0

package/src/blocks/account-button-block.tsx

@@ -3,9 +3,7 @@
 import React from 'react';
 import NextLink from 'next/link';
 import { useSession } from 'next-auth/react';
-import { usePathname } from 'next/navigation';
 import { getResponsiveValue, partAttrs } from '../utils';
-import { withReturnPath } from '../auth/auth-destination';
 import useBlockAction from '../hooks/use-block-action';
 import { BlockRendererProps } from './block-renderer-registry';
 import { readToggle } from './product-block-utils';
@@ -52,31 +50,8 @@ const AccountButtonBlock = ({
       getResponsiveValue(block.properties?.[key], currentBreakpoint, fallback)
     );
 
-  /**
-   * Whether a guest click records where the shopper was standing.
-   *
-   * On by default, and it has to be here rather than in the form: this control
-   * is the only thing that knows the answer. pz's own route guard redirects to
-   * the auth page with no parameter at all, so a login PAGE had nothing to
-   * return to — which is why the form's "go back where they came from" mode
-   * was unbuildable. Appends `?callbackUrl=<current path>`, which is the key
-   * next-auth and the brands' own views already read; the form ignores
-   * anything that is not a path on this origin.
-   *
-   * Nothing changes for a drawer: it never navigates, so there is no href to
-   * record on. A brand that tracks its login links by url turns it off.
-   */
-  const rememberReturn = readToggle(
-    block.properties?.rememberReturn,
-    currentBreakpoint,
-    true
-  );
-  const pathname = usePathname();
-
   const href = isAuthenticated
     ? prop('accountHref', '/account')
-    : rememberReturn
-    ? withReturnPath(prop('loginHref', '/auth'), pathname)
     : prop('loginHref', '/auth');
   const label = isAuthenticated
     ? prop('accountLabel', 'Account')

package/src/blocks/add-to-cart-block.tsx

@@ -10,7 +10,6 @@ import {
   emitCommerceEvent,
   readItemsCurrency
 } from '../utils/analytics';
-import { useHostModalCloser } from '../overlays/modal-host-context';
 import { BlockRendererProps } from './block-renderer-registry';
 import {
   DesignerPlaceholder,
@@ -119,19 +118,6 @@ const AddToCartBlock = ({
       getResponsiveValue(block.properties?.[key], currentBreakpoint, fallback)
     );
 
-  /**
-   * Whether finishing closes the modal this block is inside. OFF by default
-   * here, because this block's success state is something the shopper is meant
-   * to read — see `useHostModalCloser`.
-   */
-  const closeHostModalOnSuccess = readToggle(
-    block.properties?.closeHostModalOnSuccess,
-    currentBreakpoint,
-    false
-  );
-  const closeHostModal = useHostModalCloser(closeHostModalOnSuccess);
-
-
   const label = prop('label', 'Add to Cart');
   const addingLabel = prop('addingLabel', 'Adding…');
   const addedLabel = prop('addedLabel', 'Added');
@@ -300,7 +286,6 @@ const AddToCartBlock = ({
       // by the mini-basket chrome block) has to be refreshed explicitly.
       dispatch(basketApi.util.invalidateTags(['Basket', 'MiniBasket']));
       setFeedback('added');
-      closeHostModal();
       emitCommerceEvent('add_to_cart', {
         currency: readItemsCurrency(product),
         items: [buildCommerceItem(product, { quantity })]

package/src/blocks/auth-field-block.tsx

@@ -20,7 +20,7 @@ import { BlockRendererProps } from './block-renderer-registry';
  * form owns those. Standalone (outside any form) it still renders, but
  * nothing collects its value, which the designer sees immediately.
  *
- * Properties: fieldType, label, placeholder, showLabel, required, autoComplete, and for
+ * Properties: fieldType, label, placeholder, showLabel, required, and for
  * a `gender` field the two option captions (femaleLabel, maleLabel).
  * Parts: field, label, input, error.
  */
@@ -143,16 +143,6 @@ const AuthFieldBlock = ({
       : preset.type;
 
   const label = prop('label', preset.label);
-  /**
-   * What a password manager is told this box is for.
-   *
-   * The preset was compiled in, which made one screen wrong on purpose: the
-   * `password` preset says `current-password`, so a composed SIGN-UP or a
-   * reset screen told the manager to offer a saved password instead of
-   * generating a new one, and what the shopper then typed was never saved.
-   * Absent keeps the preset, so every published field is untouched.
-   */
-  const autoComplete = prop('autoComplete', '').trim() || preset.autoComplete;
   const placeholder = prop('placeholder', '');
   const showLabel = readToggle(
     block.properties?.showLabel,
@@ -226,7 +216,7 @@ const AuthFieldBlock = ({
          */
         <select
           name={controlName}
-          autoComplete={autoComplete}
+          autoComplete={preset.autoComplete}
           defaultValue=""
           aria-label={showLabel ? undefined : label}
           aria-invalid={errorMessage ? true : undefined}
@@ -245,7 +235,7 @@ const AuthFieldBlock = ({
         <input
           type={controlType}
           name={controlName}
-          autoComplete={autoComplete}
+          autoComplete={preset.autoComplete}
           placeholder={placeholder || undefined}
           aria-label={showLabel ? undefined : label}
           aria-invalid={errorMessage ? true : undefined}

package/src/blocks/auth-flow-block.tsx

@@ -1,11 +1,11 @@
 'use client';
 
 import React, { useEffect } from 'react';
-import { useSession } from 'next-auth/react';
 import { getResponsiveValue, partAttrs } from '../utils';
 import {
   ActiveAuthStepContext,
   AuthFlowIdContext,
+  DEFAULT_AUTH_FLOW_ID,
   goBackAuthStep,
   registerAuthFlowMount,
   useAuthFlowState
@@ -74,33 +74,9 @@ const AuthFlowBlock = ({
       getResponsiveValue(block.properties?.[key], currentBreakpoint, fallback)
     );
 
-  /**
-   * The name this journey answers to on the bus.
-   *
-   * Authored, it is shared: two flows carrying the same name show the same step
-   * — deliberate for one journey rendered twice, and for a trigger outside the
-   * flow that names `<flowId>:<step>`.
-   *
-   * Empty, it is the BLOCK's own, because the alternative was a collision the
-   * moment a brand did what the composition invites: a journey in the header
-   * drawer and a second one in a tab or a page body both fell back to one
-   * shared name, so opening the drawer on "register" moved the page's journey
-   * with it, and closing the drawer reset it. `DEFAULT_AUTH_FLOW_ID` stays the
-   * fallback for controls that know no flow at all — see `resolveAuthStepTarget`
-   * — so a composition that wants to be reachable that way names itself.
-   */
-  const flowId = prop('flowId', '').trim() || `flow-${block.id}`;
+  const flowId = prop('flowId', '').trim() || DEFAULT_AUTH_FLOW_ID;
   const initialStep = prop('initialStep', '').trim();
   const previewStep = prop('previewStep', '').trim();
-  /**
-   * The step a shopper who is ALREADY signed in lands on.
-   *
-   * The state picks the step, which is the flow's whole idea — so a member who
-   * opens the drawer gets "Hoş geldin / Hesabım / Çıkış" composed out of
-   * ordinary blocks instead of the login form they have no use for. Empty
-   * keeps the historical behaviour: the flow does not care about the session.
-   */
-  const signedInStep = prop('signedInStep', '').trim();
   const backLabel = prop('backLabel', 'Back');
   const showBack = readToggle(
     block.properties?.showBack,
@@ -116,13 +92,6 @@ const AuthFlowBlock = ({
   );
 
   const flowState = useAuthFlowState(isDesigner ? '' : flowId);
-  const { status } = useSession();
-  /**
-   * `loading` is not treated as signed in: the flow would open on the member
-   * step for a guest and then swap. The other way round — a member seeing the
-   * login step for a beat — is the state they are being moved out of anyway.
-   */
-  const isSignedIn = status === 'authenticated' && !isDesigner;
 
   useEffect(() => {
     if (isDesigner) return undefined;
@@ -155,20 +124,9 @@ const AuthFlowBlock = ({
       if (selected) return stepKeyOf(selected, currentBreakpoint);
     }
 
-    /**
-     * A step the shopper NAVIGATED to still wins over the member step: a
-     * signed-in shopper who taps "change password" inside the journey is
-     * asking for that step, and answering with the welcome card would be the
-     * flow overruling them. The member step is the ENTRY, so it only leads
-     * while the bus has nothing to say.
-     */
     const candidates = isDesigner
       ? [previewStep, initialStep]
-      : [
-          flowState?.active ?? '',
-          ...(isSignedIn ? [signedInStep] : []),
-          initialStep
-        ];
+      : [flowState?.active ?? '', initialStep];
 
     for (const candidate of candidates) {
       if (candidate && stepKeys.includes(candidate)) return candidate;