@wix/himalaya-cli 0.826.0 → 0.827.0

package/guides/component-reference.json

@@ -2,7 +2,7 @@
   "_comment": "GENERATED by core/web-embed/authoring/gen-reference.mjs from core/ts/src/schema.ts — do not hand-edit. The schema is the source of truth; regenerate on schema changes.",
   "schemaSource": "core/ts/src/schema.ts",
   "bindingGrammar": "$service:<service>.<path> (worker state) · $item.<field> (list row) · $flag:<key> (feature flag) · $env:<key> (client environment — #1056). Bindings resolve in the text/value props marked 'binding-aware' below — INCLUDING Modifiers token refs — but only `background` and `border.color`, which are the two whose token a binding actually fills: a worker can drive per-item theming (e.g. a game board's per-square color), not just text. `shadow` is NOT binding-aware on any renderer, and a gradient is driven by its own `backgroundGradientPath` prop resolving to a gradient token NAME, not by a binding inside a token ref — so `shadow: { token: \"$item.x\" }` and `backgroundGradient: { token: \"$item.x\" }` keep the sentinel and silently lose the per-item styling. Colour slots split by LEVEL, not by component: inside modifiers a colour is a TokenRef OBJECT ({ token: \"…\" }), inside props it is a bare TokenName STRING — there is no modifiers.color or modifiers.tint (see the 'Token slots' section in component-reference.md). A few input props render the LITERAL and are NOT binding-aware — notably SearchField.placeholder and Chip.label; SearchField.value is live and binding-aware like other content props. Bindings also CANNOT target strict-enum fields (style, size, alignment, severity, presentation, contentMode, …) — those fail at render, not validation. $env: is client-resolved (no worker) and valid in modifiers.hiddenPath and FragmentSlot.casePath ONLY — keys reduceMotion/colorScheme/sizeClass/isRTL, e.g. hiddenPath:\"$env:reduceMotion\" or hiddenPath:\"$env:colorScheme==light\", casePath:\"$env:colorScheme\"; unknown key fails open (shown / defaultCase).",
-  "componentCount": 79,
+  "componentCount": 82,
   "notImplementedComponents": [
     "FieldError",
     "Picker",
@@ -669,7 +669,35 @@
       "bindings": [
         "valuesPath"
       ],
-      "propsSource": "export interface ChartProps {\n  valuesPath?: string;\n  values?: number[];\n  /** \"line\" | \"area\" (default) | \"bar\" */\n  kind?: string;\n  color?: TokenName;\n  /** chart height in pt/dp (default 120) */\n  height?: number;\n}"
+      "propsSource": "export interface ChartProps {\n  valuesPath?: string;\n  values?: number[];\n  /** \"line\" | \"area\" (default) | \"bar\" */\n  kind?: string;\n  color?: TokenName;\n  /** chart height in pt/dp (default 120) */\n  height?: number;\n  /**\n   * Multi-series. EMPTY (or absent) ⇒ this component behaves exactly\n   * as it did before the field existed. NON-EMPTY ⇒ `values`/`valuesPath` above\n   * are ignored and the series list is the data. All series share ONE Y scale,\n   * which is the whole point: two stacked single-series Charts normalize over\n   * their own ranges independently and draw a comparison that inverts whenever\n   * the smaller series has the larger internal range.\n   */\n  series?: ChartSeries[];\n}"
+    },
+    {
+      "name": "DonutChart",
+      "category": "Analytics data-viz",
+      "propsType": "DonutChartProps",
+      "bindings": [
+        "slicesPath"
+      ],
+      "propsSource": "export interface DonutChartProps {\n  slices?: DonutSlice[];\n  /** `$service:` ONLY → [{label, value, color}] (array-valued; see ChartSeries.valuesPath). */\n  slicesPath?: string;\n  /** diameter in pt/dp (default 160) */\n  size?: number;\n  /** ring thickness in pt/dp (default 28); 0 ⇒ a solid pie */\n  thickness?: number;\n  centerTitle?: string;\n  centerSubtitle?: string;\n  /** base token for the derived opacity ramp (default \"accentPrimary\") */\n  color?: TokenName;\n}"
+    },
+    {
+      "name": "Legend",
+      "category": "Analytics data-viz",
+      "propsType": "LegendProps",
+      "bindings": [
+        "itemsPath"
+      ],
+      "propsSource": "export interface LegendProps {\n  items?: LegendItem[];\n  /** `$service:` ONLY → [{label, color, value, marker}]. */\n  itemsPath?: string;\n  /** \"horizontal\" (default, wraps) | \"vertical\" */\n  orientation?: string;\n}"
+    },
+    {
+      "name": "DataTable",
+      "category": "Analytics data-viz",
+      "propsType": "DataTableProps",
+      "bindings": [
+        "rowsPath",
+        "totalsPath"
+      ],
+      "propsSource": "export interface DataTableProps {\n  columns?: DataTableColumn[];\n  rows?: DataTableRow[];\n  /**\n   * `$service:` ONLY → an array of OBJECTS keyed by `column.key`. An array of\n   * arrays (positional, like the literal `rows`) is also accepted.\n   */\n  rowsPath?: string;\n  /**\n   * `hideHeader`, not `showHeader`: the proto field is a bool that defaults to\n   * false, so the affirmative spelling would default a table to headerless.\n   */\n  hideHeader?: boolean;\n  totals?: DataTableRow;\n  /** `$service:` ONLY → one row object. */\n  totalsPath?: string;\n  /** 0 / absent ⇒ unbounded */\n  maxRows?: number;\n  zebra?: boolean;\n}"
     },
     {
       "name": "VoiceNote",

package/guides/component-reference.md

@@ -3,7 +3,7 @@
 > GENERATED from `core/ts/src/schema.ts` by `core/web-embed/authoring/gen-reference.mjs`.
 > The schema is the source of truth — regenerate on schema changes; do not hand-edit.
 
-**79 core component types.** Every component body is `{ "package": "himalaya", "type": "<Type>", "props": { … } }`.
+**82 core component types.** Every component body is `{ "package": "himalaya", "type": "<Type>", "props": { … } }`.
 Binding grammar: `$service:<service>.<path>` (worker state) · `$item.<field>` (list row template) · `$flag:<key>` (feature flag) · `$env:<key>` (client environment — #1056).
 Bindings resolve in the text/value props marked **binding-aware** below — **including two `Modifiers` token refs**, `background` and `border.color`, which are the only two whose token a binding actually fills: a worker can drive per-item **theming** (e.g. a game board's per-square color, `background: { token: "$item.bg" }`), not just text content. `shadow` and `backgroundGradient` are `TokenRef`s but are **not** binding-aware on any renderer — `shadow: { token: "$item.x" }` keeps the sentinel as a literal token name and silently loses the per-item styling, and a gradient is driven by its own `backgroundGradientPath` prop resolving to a gradient token NAME, not by a binding inside a token ref.
 `$env:` is **client-resolved** (no worker) and valid in `modifiers.hiddenPath` and `FragmentSlot.casePath` **only** — keys `reduceMotion` / `colorScheme` / `sizeClass` / `isRTL`, with an optional `==`/`!=` comparison (e.g. `hiddenPath: "$env:reduceMotion"`, `hiddenPath: "$env:colorScheme==light"`, `casePath: "$env:colorScheme"`). An unknown key fails open (shown / `defaultCase`).
@@ -89,6 +89,9 @@ See also **[Modifiers](#modifiers)** (the `modifiers` block) and **[Actions](#ac
 | `Gauge` | Display & data-viz | `valuePath`, `tintPath` |
 | `Rating` | Display & data-viz | `valuePath` |
 | `Chart` | Display & data-viz | `valuesPath` |
+| `DonutChart` | Analytics data-viz | `slicesPath` |
+| `Legend` | Analytics data-viz | `itemsPath` |
+| `DataTable` | Analytics data-viz | `rowsPath`, `totalsPath` |
 | `VoiceNote` | Recorded-audio bubble (messenger design G4) | `waveformPath`, `durationMsPath`, `positionMsPath`, `statePath`, `deliveryPath`, `ratePath` |
 | `Marquee` | Recorded-audio bubble (messenger design G4) | — |
 | `Timeline` | Recorded-audio bubble (messenger design G4) | `entriesPath` |
@@ -111,7 +114,7 @@ See also **[Modifiers](#modifiers)** (the `modifiers` block) and **[Actions](#ac
 
 These props are accepted by the schema and pass validation, but the named platform's renderer never reads them — they silently do nothing (no warning, no log). Prefer a prop NOT listed here, or drive the behaviour from a worker.
 
-**Scope: 14 of 79 components, all of them ios-only** — every other component/platform pair reads every prop it decodes. The list splits in two, and the halves mean different things:
+**Scope: 14 of 82 components, all of them ios-only** — every other component/platform pair reads every prop it decodes. The list splits in two, and the halves mean different things:
 
 - **`category` (4: `BottomSheet`, `Menu`, `Tooltip`, `Popover`)** — the prop changes the component's *kind*. These genuinely are **not implemented**: an overlay renders always-visible inline, so the component does not do the job its name implies. Check the row's note for a working alternative — for a dismissible sheet it is `presentation: "sheet"` on the navigating `Action`, not `BottomSheet`.
 - **`styling` (10: `FieldError`, `Picker`, `DatePicker`, `Tabs`, `Snackbar`, `Slider`, `ActivityIndicator`, `ChipsInput`, `OtpInput`, `Video`)** — the component itself **works**; only the listed prop is inert. `Slider` on iOS is a working slider whose `debounceMs` does not throttle — not a broken `Slider`. Use the component; just do not depend on that one prop.
@@ -164,7 +167,7 @@ So `border` nests an object and `boxShadow`/`backgroundGradient` nest strings. R
 element interface (printed below) rather than extrapolating from the level.
 
 - Modifier-level (`TokenRef` object): `modifiers.background`, `modifiers.shadow`, `modifiers.backgroundGradient`, `modifiers.appear`, `modifiers.material`, `modifiers.pressMotion`, `modifiers.border.color`.
-- Component-prop-level (bare `TokenName` string): `Card.background`, `Text.style`, `Text.color`, `Image.placeholder`, `Image.tint`, `Icon.tint`, `Toggle.trackOn`, `Toggle.trackOff`, `Toggle.thumb`, `Badge.token`, `Tag.token`, `ProgressBar.tint`, `ProgressBar.trackColor`, `ListItem.titleStyle`, `ListItem.subtitleStyle`, `ListItem.titleColor`, `ListItem.subtitleColor`, `ListItem.overlineColor`, `Slider.tint`, `ActivityIndicator.tint`, `Chip.token`, `Label.style`, `Label.color`, `Gauge.tint`, `Rating.color`, `Chart.color`, `VoiceNote.tint`, `Marquee.style`, `Marquee.color`, `Fab.tint`.
+- Component-prop-level (bare `TokenName` string): `Card.background`, `Text.style`, `Text.color`, `Image.placeholder`, `Image.tint`, `Icon.tint`, `Toggle.trackOn`, `Toggle.trackOff`, `Toggle.thumb`, `Badge.token`, `Tag.token`, `ProgressBar.tint`, `ProgressBar.trackColor`, `ListItem.titleStyle`, `ListItem.subtitleStyle`, `ListItem.titleColor`, `ListItem.subtitleColor`, `ListItem.overlineColor`, `Slider.tint`, `ActivityIndicator.tint`, `Chip.token`, `Label.style`, `Label.color`, `Gauge.tint`, `Rating.color`, `Chart.color`, `DonutChart.color`, `VoiceNote.tint`, `Marquee.style`, `Marquee.color`, `Fab.tint`.
 
 There is **no `modifiers.color` and no `modifiers.tint`** — a `tint` is always a component
 prop. Of the two nested slots spelled `color`, `modifiers.border.color` is a `TokenRef`
@@ -1295,6 +1298,72 @@ export interface ChartProps {
   color?: TokenName;
   /** chart height in pt/dp (default 120) */
   height?: number;
+  /**
+   * Multi-series. EMPTY (or absent) ⇒ this component behaves exactly
+   * as it did before the field existed. NON-EMPTY ⇒ `values`/`valuesPath` above
+   * are ignored and the series list is the data. All series share ONE Y scale,
+   * which is the whole point: two stacked single-series Charts normalize over
+   * their own ranges independently and draw a comparison that inverts whenever
+   * the smaller series has the larger internal range.
+   */
+  series?: ChartSeries[];
+}
+```
+
+### Analytics data-viz
+
+#### DonutChart
+
+```ts
+export interface DonutChartProps {
+  slices?: DonutSlice[];
+  /** `$service:` ONLY → [{label, value, color}] (array-valued; see ChartSeries.valuesPath). */
+  slicesPath?: string;
+  /** diameter in pt/dp (default 160) */
+  size?: number;
+  /** ring thickness in pt/dp (default 28); 0 ⇒ a solid pie */
+  thickness?: number;
+  centerTitle?: string;
+  centerSubtitle?: string;
+  /** base token for the derived opacity ramp (default "accentPrimary") */
+  color?: TokenName;
+}
+```
+
+#### Legend
+
+```ts
+export interface LegendProps {
+  items?: LegendItem[];
+  /** `$service:` ONLY → [{label, color, value, marker}]. */
+  itemsPath?: string;
+  /** "horizontal" (default, wraps) | "vertical" */
+  orientation?: string;
+}
+```
+
+#### DataTable
+
+```ts
+export interface DataTableProps {
+  columns?: DataTableColumn[];
+  rows?: DataTableRow[];
+  /**
+   * `$service:` ONLY → an array of OBJECTS keyed by `column.key`. An array of
+   * arrays (positional, like the literal `rows`) is also accepted.
+   */
+  rowsPath?: string;
+  /**
+   * `hideHeader`, not `showHeader`: the proto field is a bool that defaults to
+   * false, so the affirmative spelling would default a table to headerless.
+   */
+  hideHeader?: boolean;
+  totals?: DataTableRow;
+  /** `$service:` ONLY → one row object. */
+  totalsPath?: string;
+  /** 0 / absent ⇒ unbounded */
+  maxRows?: number;
+  zebra?: boolean;
 }
 ```
 

package/guides/index.json

@@ -1,7 +1,7 @@
 {
   "_comment": "AUTO-GENERATED by tools/authoring-kit/bundle.mjs — DO NOT EDIT. Regenerate with: npm run authoring:gen",
   "schemaStamp": {
-    "componentCount": 79,
+    "componentCount": 82,
     "schemaSource": "core/ts/src/schema.ts"
   },
   "portalUrl": "https://bo.wix.com/_api/himalaya-admin/admin-standalone/#/developer",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.826.0",
+  "version": "0.827.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -63,5 +63,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "b3bc4ec44896b4a76de319d7e7785fdec50e5682c47183f97304d771"
+  "falconPackageHash": "1f67eedd183563d5753b32ea4eb82f8764a58881413ef36f01f8324c"
 }