@mohasinac/appkit 4.42.1 → 4.42.3

package/dist/features/seller/hooks/useSellerListingData.d.ts

@@ -14,5 +14,4 @@ type UnknownRecord = Record<string, JsonValue>;
 export declare function toRecordArray(value: unknown): UnknownRecord[];
 export declare function toStringValue(value: unknown, fallback?: string): string;
 export declare function toCurrency(value: unknown): string;
-export declare function toRelativeDate(value: unknown): string;
 export {};

package/dist/features/seller/hooks/useSellerListingData.js

@@ -18,25 +18,23 @@ export function toCurrency(value) {
     }
     return formatCurrency(value);
 }
-export function toRelativeDate(value) {
-    const date = parseDate(value);
-    if (!date) {
-        return "-";
-    }
-    const deltaMs = Date.now() - date.getTime();
-    const minute = 60000;
-    const hour = 60 * minute;
-    const day = 24 * hour;
-    if (deltaMs < minute)
-        return "just now";
-    if (deltaMs < hour)
-        return `${Math.floor(deltaMs / minute)}m ago`;
-    if (deltaMs < day)
-        return `${Math.floor(deltaMs / hour)}h ago`;
-    if (deltaMs < 7 * day)
-        return `${Math.floor(deltaMs / day)}d ago`;
-    return date.toLocaleDateString("en-IN", { year: "numeric", month: "short", day: "numeric" });
-}
+/*
+ * 🛑 `toRelativeDate` WAS HERE AND IS GONE. Import it from
+ * `features/admin/hooks/useAdminListingData` — the defining module now, and
+ * the one 44 files already use (Root Cause #18: import from where a symbol is
+ * defined, never from a convenience copy).
+ *
+ * This copy had drifted from that one and the drift was live: for a FUTURE
+ * date, `deltaMs` is negative, so `deltaMs < minute` matched and this version
+ * answered **"just now"** while the admin version answered **"1m ago"** — two
+ * different wrong answers to "when is this deadline", depending on which file
+ * a view happened to import from. The admin one is fixed to say "in 48h"; a
+ * second implementation is how that fix would have been half-applied.
+ *
+ * The three sibling helpers below are also duplicated there. They are left
+ * alone deliberately: none of them is wrong, and collapsing them is an import
+ * rewrite across both feature trees rather than a bug fix.
+ */
 function parseDate(value) {
     if (value instanceof Date)
         return value;

package/dist/features/shell/SectionForm.js

@@ -10,6 +10,9 @@ import { useFormBottomActions } from "../layout/hooks/useFormBottomActions";
 import { useSectionState } from "../account/hooks/useCollapsedSections";
 import { FormSchemaContext } from "./FormShell";
 import { EASE_OUT_MS } from "../../tokens/motion";
+/* Stable identity — a fresh `{}` per render would break any memo a section
+ * render does on its `errors` prop. */
+const EMPTY_ERRORS = {};
 /** Sections in render order: required first, original order preserved within each group. */
 export function orderSections(sections) {
     return [...sections.filter((s) => s.required), ...sections.filter((s) => !s.required)];
@@ -118,6 +121,27 @@ export function SectionForm({ sections, values, onChange, onSubmit, submitLabel
      * a caller renders it outside a provider, which is legitimate.
      */
     const shellCtx = useContext(FormShellContext);
+    /*
+     * 🛑 Has the user ASKED to save yet?
+     *
+     * Root Cause #74 gated `FormErrorSummary` on this and stopped there. The
+     * per-section "N issues" badges below were never gated, and the eleven views
+     * that mount SectionForm all call `validate(draft)` from a MOUNT EFFECT —
+     * which that entry is explicit must STAY, because it is what keeps the errors
+     * current as the user fixes fields after a failed save. So `fieldErrors` is
+     * fully populated on first paint, and "Add New Address" opened reading
+     * "3 issues" and "4 issues" in red against a form nobody had typed into.
+     *
+     * Gate the DISPLAY, never the computation — deleting the mount-effect
+     * validate is the obvious repair and it is the wrong one.
+     *
+     * Local state rather than `shellCtx.submitAttempted` alone: SectionForm owns
+     * the submit button, so it always knows, whereas `shellCtx` is legitimately
+     * null when a caller renders it outside a provider (see above). Both are
+     * consulted, so a provider-level attempt from the pinned mobile bar counts too.
+     */
+    const [attemptedHere, setAttemptedHere] = useState(false);
+    const submitAttempted = attemptedHere || shellCtx?.submitAttempted === true;
     const [fieldErrors, setFieldErrors] = useState({});
     const [uncontrolledOpenIds, setUncontrolledOpenIds] = useState(() => orderSections(sections).filter((s) => s.required).map((s) => s.id));
     /*
@@ -251,6 +275,7 @@ export function SectionForm({ sections, values, onChange, onSubmit, submitLabel
      * identically whichever the user presses.
      */
     const handleSubmit = useCallback(() => {
+        setAttemptedHere(true);
         shellCtx?.markSubmitAttempted();
         /*
          * Reveal the FIRST offending section — only the first. Expanding all five
@@ -328,9 +353,15 @@ export function SectionForm({ sections, values, onChange, onSubmit, submitLabel
                      * <button><div><span><div> — invalid, since a button may only
                      * contain phrasing content. Same variant props, legal element.
                      */
-                    _jsxs(Row, { as: "span", align: "center", gap: "xs", className: "min-w-0", children: [_jsx(Span, { weight: "semibold", size: "sm", children: section.heading ?? section.label }), isRequired && _jsx(Span, { size: "xs", color: "muted", children: "Required" })] }), isCollapsed: isCollapsed, collapsible: !isRequired, onToggle: () => toggle(section.id), keepMounted: section.keepMounted, renderHeaderExtra: errorCount > 0
+                    _jsxs(Row, { as: "span", align: "center", gap: "xs", className: "min-w-0", children: [_jsx(Span, { weight: "semibold", size: "sm", children: section.heading ?? section.label }), isRequired && _jsx(Span, { size: "xs", color: "muted", children: "Required" })] }), isCollapsed: isCollapsed, collapsible: !isRequired, onToggle: () => toggle(section.id), keepMounted: section.keepMounted, renderHeaderExtra: 
+                    /* Only after the user has tried to save — see `submitAttempted` above. */
+                    submitAttempted && errorCount > 0
                         ? () => (_jsxs(Badge, { variant: "danger", children: [errorCount, " ", errorCount === 1 ? "issue" : "issues"] }))
-                        : undefined, children: section.render({ values, onChange: handleFieldChange, errors: fieldErrors }) }, section.id));
+                        : undefined, children: section.render({
+                        values,
+                        onChange: handleFieldChange,
+                        errors: submitAttempted ? fieldErrors : EMPTY_ERRORS,
+                    }) }, section.id));
             }), !hideActions && (
             /*
              * `justify="between"` so a destructive action sits opposite Save

package/dist/features/tester/seed-data/_happy-path.d.ts

@@ -0,0 +1,23 @@
+import type { TesterCaseRole } from "../schemas";
+interface HappyPathCase {
+    key: string;
+    label: string;
+    /** Every role the case affects; per-role detail goes inline in the expectations. */
+    roles: TesterCaseRole[];
+    startPage?: string;
+    steps: string[];
+    inputs?: Record<string, string | number | boolean>;
+    expectedBehaviour: string;
+    expectedUiState: string;
+    expectedData?: Record<string, string | number | boolean>;
+    endResult: string;
+    href?: string;
+}
+interface HappyPathPage {
+    pageKey: string;
+    pageLabel: string;
+    href?: string;
+    cases: HappyPathCase[];
+}
+export declare const happyPathPages: HappyPathPage[];
+export {};