@rokt/dcui-orchestrator 1.2.1-rc.11 → 1.2.1-rc.13

package/dist/modules/instant-purchase/src/components/catalog-selectors-stacked/catalog-selectors-stacked.d.ts

@@ -2,9 +2,9 @@ import React from 'react';
 import { CatalogSelectorsStackedModel, LayoutSchemaModel, WhenPredicate } from '@rokt/dcui-layout-schema';
 export interface CatalogSelectorsStackedProps<Template extends LayoutSchemaModel> {
     /**
-     *  - `default`: the template rendered once per variant dimension. Each render
-     *    resolves the dimension it is rendering, so one shared template can label
-     *    itself:
+     *  - `default`: the template rendered once per variant dimension.
+     *    `CatalogDropdown` includes its own visible dimension label. Do not add a
+     *    separate label node. Each render also exposes tokens for custom content:
      *    * `%^DATA.variantAttribute.attributeId^%`: the dimension id, e.g.
      *      `color`. It comes from the merchant's variant option key and is
      *      neither normalised nor guaranteed lowercase or single-word, so
@@ -12,22 +12,15 @@ export interface CatalogSelectorsStackedProps<Template extends LayoutSchemaModel
      *      `text.textTransform` rather than transforming the value, so `When`
      *      comparisons stay stable.
      *    * `%^DATA.variantAttribute.hasMultipleOptions^%`: `"true"` or `"false"`.
-     *      `CatalogDropdown` renders nothing for a single option, so a label
-     *      would otherwise sit above no control. Gate the label on this.
+     *      `CatalogDropdown` renders neither label nor control for a single option.
      *    Tokens from the enclosing scope stay resolvable alongside these.
      *
-     *    Put a `When` on `hasMultipleOptions` around the label node **only**, and
-     *    keep `CatalogDropdown` as its sibling:
-     *
-     *        Column [ When(hasMultipleOptions is "true") [ BasicText ],
-     *                 CatalogDropdown ]
-     *
-     *    A `When` that encloses the dropdown instead would stop it mounting, and
+     *    Keep the dropdown mounted. A `When` that encloses it would stop it mounting, and
      *    a dropdown that never mounts never registers its validator field key —
      *    a trigger that then resolves zero keys fails closed, blocking the CTA
      *    with nothing on screen to explain it.
      *
-     *    Bind the label with `BasicText`. `RichText` sends the value through the
+     *    Bind custom text with `BasicText`. `RichText` sends the value through the
      *    HTML sanitiser, which throws on markup-shaped input; the node is then
      *    dropped by its error boundary.
      *  - `dropdown`: accepted by the layout schema, currently ignored — this

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rokt/dcui-orchestrator",
-  "version": "1.2.1-rc.11",
+  "version": "1.2.1-rc.13",
   "description": "Rokt's DCUI rendering process",
   "main": "dist/index.cjs",
   "module": "dist/index.js",