codexly-ui 0.10.68 → 0.10.70

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codexly-ui",
-  "version": "0.10.68",
+  "version": "0.10.70",
   "description": "Standalone, signal-based Angular UI component library for Codexly, styled with Tailwind CSS.",
   "keywords": [
     "angular",

package/types/codexly-ui.d.ts

@@ -3006,6 +3006,13 @@ declare class ClxProductDetailComponent {
      *  panels visually consistent with the rest of the e-commerce card set. */
     protected readonly _panelClass = "bg-clx-surface rounded-2xl shadow-sm p-4";
     readonly tabItems: ClxTabItem[];
+    /** Tracks which product the spec selection was initialized for — the init effect below must run
+     *  once per actual product change, not every time initialVariationId() changes. A host app that
+     *  syncs its own ?variant= URL param from the (variationChange) output (see codexly-store's
+     *  product-detail page) feeds that id back into this same input; without this guard, every spec
+     *  click would round-trip through the host and re-trigger initialization, silently overwriting
+     *  the visitor's in-progress selection with the just-resolved variation's full spec set. */
+    private _initializedForProductId;
     constructor();
     /** With no specs selected (fresh load, or every spec toggled back off) this is the variation
      *  the visitor originally landed on. Otherwise, resolves the variation matching every currently
@@ -3013,6 +3020,16 @@ declare class ClxProductDetailComponent {
      *  whose specs are a superset of the selection counts as a match, since the visitor hasn't
      *  narrowed those other spec types down to one value yet. */
     readonly activeVariation: _angular_core.Signal<ClxVariation | null>;
+    /** True only once the visitor has explicitly picked one option per spec type (Color AND Talla,
+     *  not just one of them) — activeVariation() always resolves to *some* variation even with a
+     *  partial selection (see its own doc comment), so it alone can't gate the CTA: without this,
+     *  "Agrega al carrito" would add whatever variation the partial selection happened to resolve to
+     *  (e.g. the first in-stock Talla under the chosen Color) instead of what the visitor actually
+     *  chose. */
+    readonly isSelectionComplete: _angular_core.Signal<boolean>;
+    /** Names of the spec types still missing a selection — surfaced next to the CTA so a disabled
+     *  "Agrega al carrito" reads as "pick a Talla" instead of an unexplained dead button. */
+    readonly missingSpecNames: _angular_core.Signal<string[]>;
     readonly finalPrice: _angular_core.Signal<number>;
     readonly discount: _angular_core.Signal<number>;
     /** An option is available if some in-stock variation matches it together with the rest of the