@object-ui/plugin-dashboard 17.3.0 → 17.6.0

package/README.md

@@ -16,6 +16,30 @@ Dashboard plugin for Object UI - Create beautiful dashboards with metrics, chart
 pnpm add @object-ui/plugin-dashboard
 ```
 
+## Requires a bundler — plain Node cannot import this package
+
+`DashboardGridLayout` imports `react-grid-layout`'s stylesheet at module scope
+(`import 'react-grid-layout/css/styles.css'`), and Node has no loader for `.css` at all.
+Importing the published entry from plain Node ESM — no bundler, no loader hooks — therefore
+resolves and then fails during evaluation:
+
+```text
+TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".css"
+  for .../react-grid-layout/css/styles.css
+```
+
+**This is a supported-configuration statement, not a bug to report.** Unbundled Node
+consumption is not supported for style-carrying plugin packages. It was ruled that way on
+[objectui#5384](https://github.com/objectstack-ai/objectui/issues/5384) — deliberately, over
+the alternative of moving the stylesheet out of module scope — because the grid's layout rules
+are not optional and no unbundled-Node consumer exists to serve.
+
+Consume it through a host that handles CSS imports, which every supported host does: Vite,
+webpack, or Next with the package listed in `transpilePackages`. If you have a real need to
+import it under plain Node — SSR with no bundler, a Node-side script — please open an issue.
+That reopens the question as a design decision rather than a defect, and the shape of your
+consumer is the missing input.
+
 ## Usage
 
 ### Automatic Registration (Side-Effect Import)
@@ -39,18 +63,62 @@ const schema = {
 };
 ```
 
-### Manual Registration
+### What the side-effect import registers
+
+That single import is the whole of registration — there is no components map to
+iterate over. Importing the entry runs the eight `ComponentRegistry.register(...)`
+calls in `src/index.tsx`, which claim exactly these schema types. The keys below
+are read off those calls:
+
+| Namespaced key | Bare-name fallback | Renderer behind it |
+| --- | --- | --- |
+| `view:dashboard` | `dashboard` | `DashboardRenderer` — the widget container |
+| `plugin-dashboard:metric` | `metric` | `MetricWidget` — one KPI value |
+| `plugin-dashboard:metric-card` | `metric-card` | `MetricCard` — KPI with trend and icon |
+| `plugin-dashboard:object-metric` | `object-metric` | internal wrapper around `ObjectMetricWidget` — aggregates over an object |
+| `plugin-dashboard:pivot` | `pivot` | `PivotTable` — pivot over rows you pass in |
+| `plugin-dashboard:object-pivot` | `object-pivot` | internal wrapper around `ObjectPivotTable` — pivot queried from an object |
+| `plugin-dashboard:dashboard-grid` | `dashboard-grid` | `DashboardGridLayout` — the drag/resize editable grid |
+| `plugin-dashboard:object-data-table` | `object-data-table` | `ObjectDataTable` — table queried from an object |
+
+`ComponentRegistry.register` publishes `namespace:type`, and — unless the call
+passes `skipFallback: true` — the bare `type` as a back-compat fallback
+(`packages/core/src/registry/Registry.ts:194`, fallback branch at `:226`). No
+call in this package passes `skipFallback`, so each type above resolves under
+both spellings. The two `object-*` types are served by internal wrappers that
+first resolve the spec's per-element `dataSource` binding (through
+`ElementDataSourceGate` from `@object-ui/react`) and then render the exported
+component, which is why those rows name a wrapper rather than an export.
+
+### Registering a component under your own key
+
+To serve one of this package's components under a key of your own, register the
+exported component — that is what a manual registration is here:
 
 ```typescript
-import { dashboardComponents } from '@object-ui/plugin-dashboard';
 import { ComponentRegistry } from '@object-ui/core';
+import { MetricCard } from '@object-ui/plugin-dashboard';
 
-// Register dashboard components
-Object.entries(dashboardComponents).forEach(([type, component]) => {
-  ComponentRegistry.register(type, component);
+ComponentRegistry.register('my-metric', MetricCard, {
+  namespace: 'my-app',
+  label: 'My Metric',
+  category: 'Dashboard',
 });
 ```
 
+There is also a `dashboardComponents` export: the manual-integration map, keyed
+by the **same eight schema types** as the table above (objectui#5064 re-keyed it
+from component class names). Each key maps to the exact component the import
+registers for that type — for the two `object-*` types that is the internal
+data-source-gate wrapper, not the exported widget. Iterating it with
+`ComponentRegistry.register(type, component)` therefore re-registers the eight
+types the import has already claimed, which is still not the manual registration
+above: each such call passes no `meta`, so it trips the no-namespace deprecation
+warning in `register` (`packages/core/src/registry/Registry.ts:198`) and
+rewrites each bare-name registry entry without its `label`/`category` metadata
+(the `namespace:type` entries are untouched). The side-effect import remains the
+whole of registration.
+
 ## Schema API
 
 ### Dashboard
@@ -219,21 +287,36 @@ into each bound widget's inline query (`AND`-combined with the widget's own
       "field": "region",            // default binding target
       "label": "Region",
       "type": "select",             // text | select | date | number | lookup
-      "options": ["EMEA", "APAC", "AMER"]
+      // Canonical @objectstack/spec pair form — the only form the platform
+      // accepts at publish. The bare-string shorthand (["EMEA", …]) is
+      // deprecated: still lifted at runtime, now warns (objectui#4356).
+      "options": [
+        { "value": "EMEA", "label": "EMEA" },
+        { "value": "APAC", "label": "APAC" },
+        { "value": "AMER", "label": "AMER" }
+      ]
       // or dynamic: "optionsFrom": { "object": "accounts", "valueField": "region" }
     }
   ],
   "widgets": [
+    // Widgets bind a semantic-layer dataset (ADR-0021) and select its
+    // dimensions/measures by name. The pre-ADR-0021 top-level `object` +
+    // `categoryField`/`valueField`/`aggregate` shape was REMOVED — a widget
+    // still carrying it renders "This widget uses a retired data format.
+    // Edit it to bind a dataset." instead of a chart. A renderer-internal
+    // query lives under `options.data` as `{ provider: 'object', object,
+    // aggregate }`; an `options.data` array is fixed demo data.
+    //
     // Default binding: the filter's own `field` (dateRange → created_at).
-    { "id": "w1", "type": "bar", "object": "invoices", "aggregate": "count" },
+    { "id": "w1", "type": "bar", "dataset": "invoices", "dimensions": ["status"], "values": ["count"] },
     // Explicit binding: map each filter to THIS widget's own field.
     {
-      "id": "w2", "type": "line", "object": "accounts", "aggregate": "count",
+      "id": "w2", "type": "line", "dataset": "accounts", "dimensions": ["signed_month"], "values": ["count"],
       "filterBindings": { "dateRange": "signed_at", "region": "sales_region" }
     },
     // Opt out of a filter with `false`.
     {
-      "id": "w3", "type": "metric", "object": "invoices", "aggregate": "count",
+      "id": "w3", "type": "metric", "dataset": "invoices", "values": ["count"],
       "filterBindings": { "region": false }
     }
   ]
@@ -267,26 +350,106 @@ Notes:
   warning instead of emitting a query that matches nothing. Explicit
   `filterBindings` strings are always honoured as written.
 
-## TypeScript Support
+## Widget accent colour (`colorVariant`)
+
+A KPI widget can declare a semantic accent. The vocabulary is
+`@objectstack/spec`'s `WidgetColorVariantSchema` enum — `default`, `blue`,
+`teal`, `orange`, `purple`, `success`, `warning`, `danger` — the same eight
+tokens the designer's swatch picker offers:
 
 ```typescript
-import type { DashboardSchema, MetricCardSchema } from '@object-ui/plugin-dashboard';
+{
+  id: 'kpi_at_risk',
+  type: 'metric',
+  title: 'At-Risk Projects',
+  dataset: 'project_health',
+  values: ['project_count'],
+  filter: { health: 'red' },
+  colorVariant: 'danger',   // tints the value; card chrome stays neutral
+}
+```
 
-const metricCard: MetricCardSchema = {
-  type: 'metric-card',
+Where the accent lands depends on the layout, not on the token:
+
+| Layout | Accent |
+| --- | --- |
+| Card chrome (`MetricWidget`, inline `object-metric`) | the icon chip's background + foreground |
+| Chrome-less (`MetricWidget variant: 'bare'`, and every dataset-bound `metric`) | the big number's text colour |
+
+Both read one shared table (`src/colorVariants.ts`), so the same declaration
+reads the same on either surface. `default` — and omitting the key — means "no
+accent"; the widget renders in the ambient foreground colour. A token outside
+the enum gets no accent and is not aliased to a nearby colour: it is invalid
+metadata, rejected where it is authored and published rather than reinterpreted
+here.
+
+## TypeScript Support
+
+This package ships **components, not schema types** — its whole type export
+surface is `WidgetConfigPanelProps`, `ConfigPanelTranslate` and the three
+`WidgetDataset*` catalog types, none of which describe an authored dashboard.
+The authored shape is typed by `@object-ui/types`:
+
+| Import from `@object-ui/types` | What it types |
+| --- | --- |
+| `DashboardComponentSchema` | the whole `type: 'dashboard'` node — `columns`, `gap`, `widgets`, `header`, `globalFilters`, `dateRange`, `refreshInterval`, … |
+| `DashboardWidgetSchema` | one entry of `widgets[]` — the spec's `DashboardWidget` keys, plus objectui's own (`component`, `layout`, `options`, …) |
+| `DashboardWidgetLayout` | a widget's `{ x, y, w, h }` grid box |
+
+```typescript
+import type {
+  DashboardComponentSchema,
+  DashboardWidgetSchema,
+} from '@object-ui/types';
+
+// Dataset-bound KPI — the widget vocabulary (see "Dashboard-level filters").
+const revenue: DashboardWidgetSchema = {
+  id: 'kpi_revenue',
+  type: 'metric',
   title: 'Revenue',
-  value: '$123,456',
-  trend: 'up',
-  trendValue: '+12%'
+  dataset: 'invoices',
+  values: ['count'],
+  colorVariant: 'success',
+};
+
+// Single-value widget with no query: the number lives under `options`.
+const users: DashboardWidgetSchema = {
+  id: 'kpi_users',
+  type: 'metric',
+  title: 'Total Users',
+  options: { value: '1,234' },
+};
+
+// Component format: a registered component node in the widget's `component`
+// slot. Its keys are that COMPONENT's props, not widget keys.
+const custom: DashboardWidgetSchema = {
+  id: 'kpi_custom',
+  component: {
+    type: 'metric-card',
+    title: 'Revenue',
+    value: '$123,456',
+    trend: 'up',
+    trendValue: '+12%',
+  },
+  layout: { x: 0, y: 0, w: 3, h: 2 },
 };
 
-const dashboard: DashboardSchema = {
+const dashboard: DashboardComponentSchema = {
   type: 'dashboard',
   columns: 3,
-  widgets: [metricCard]
+  gap: 4,
+  widgets: [revenue, users, custom],
 };
 ```
 
+There is **no per-widget-family schema type**: one `DashboardWidgetSchema`
+covers every `type` (`metric`, `bar`, `table`, …) and the family-specific
+settings live under `options`. `MetricCard`'s own props — `value`, `trend`,
+`trendValue` — are the component's, not the widget's: `DashboardWidgetSchema`
+declares none of them, and the component's props interface is not on this
+package's export surface either. So a `metric-card` node is typed only where it
+appears as a component (the `component` slot above), not as a widget family.
+
 ## Customization
 
 All components support Tailwind CSS classes:
@@ -342,9 +505,7 @@ auto-detection.
 }
 ```
 
-## DashboardGridLayout — persisting drag / resize edits
-
-### DashboardRenderer — design-mode widget reorder
+## DashboardRenderer — design-mode widget reorder
 
 When `DashboardRenderer` is used in design mode (`designMode={true}` plus an
 `onWidgetsReorder` callback), widgets become sortable via
@@ -369,10 +530,26 @@ through the `onSchemaChange` callback.
 <DashboardGridLayout
   schema={dashboard}
   // ✅ Preferred — write the updated schema through your data adapter.
-  onSchemaChange={(next) => client.meta.saveItem('dashboard', next.name, next)}
+  onSchemaChange={(next) => {
+    // `name` is optional on the schema, and `saveItem` requires it — decide
+    // what an unnamed dashboard means to your host instead of writing through.
+    if (!next.name) return;
+    client.meta.saveItem('dashboard', next.name, next);
+  }}
 />
 ```
 
+The guard is not defensive noise: the callback receives a
+`DashboardComponentSchema`, whose `name` is optional (`BaseSchema.name` in
+`@object-ui/types`), while `client.meta.saveItem(type, name, item)` declares
+`name: string`. Passing `next.name` straight through is `TS2345` under `strict`
+(`Argument of type 'string | undefined' is not assignable to parameter of type
+'string'`), so a copied snippet does not compile — and what the server does with
+an absent name has **not** been measured here, which is the other reason this
+example declines to send one rather than guessing. A host that already knows
+which metadata item the grid is editing should pass that name from its own state
+instead of reading it off the node.
+
 If `onSchemaChange` is **not** provided, layout edits stay in component
 state and are lost on refresh — a `console.warn` is emitted in development
 to flag the missing wiring. The component never writes to `localStorage`
@@ -386,17 +563,6 @@ file system, …) per the protocol-agnostic architecture rule.
 > dashboards. If you still want a browser-local cache for a demo, do it
 > in the parent inside `onSchemaChange`.
 
-<!-- release-metadata:v3.3.0 -->
-
-## Compatibility
-
-- **React:** 18.x or 19.x
-- **Node.js:** ≥ 18
-- **TypeScript:** ≥ 5.0 (strict mode)
-- **`@objectstack/spec`:** ^3.3.0
-- **`@objectstack/client`:** ^3.3.0
-- **Tailwind CSS:** ≥ 3.4 (for packages with UI)
-
 ## Links
 
 - 📚 [Documentation](https://www.objectui.org/docs/plugins/plugin-dashboard)

package/dist/DashboardConfigPanel.d.ts

@@ -1,3 +1,5 @@
+import { ConfigPanelSchema } from '@object-ui/components';
+import { ConfigPanelTranslate } from './useConfigPanelTranslation';
 /**
  * ObjectUI
  * Copyright (c) 2024-present ObjectStack Inc.
@@ -6,6 +8,7 @@
  * LICENSE file in the root directory of this source tree.
  */
 import * as React from 'react';
+export declare function buildDashboardSchema(t: ConfigPanelTranslate): ConfigPanelSchema;
 export interface DashboardConfigPanelProps {
     /** Whether the panel is open */
     open: boolean;

package/dist/DashboardConfigPanel.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DashboardConfigPanel.d.ts","sourceRoot":"","sources":["../src/DashboardConfigPanel.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAkH/B,MAAM,WAAW,yBAAyB;IACxC,gCAAgC;IAChC,IAAI,EAAE,OAAO,CAAC;IACd,oBAAoB;IACpB,OAAO,EAAE,MAAM,IAAI,CAAC;IACpB,kDAAkD;IAClD,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAC5B,iCAAiC;IACjC,MAAM,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,KAAK,IAAI,CAAC;IAC9C,oCAAoC;IACpC,aAAa,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,IAAI,CAAC;CACrD;AAMD;;;;;;GAMG;AACH,wBAAgB,oBAAoB,CAAC,EACnC,IAAI,EACJ,OAAO,EACP,MAAM,EACN,MAAM,EACN,aAAa,GACd,EAAE,yBAAyB,qBAiB3B"}
+{"version":3,"file":"DashboardConfigPanel.d.ts","sourceRoot":"","sources":["../src/DashboardConfigPanel.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAK/B,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAC/D,OAAO,EAEL,KAAK,oBAAoB,EAC1B,MAAM,6BAA6B,CAAC;AA2CrC,wBAAgB,oBAAoB,CAAC,CAAC,EAAE,oBAAoB,GAAG,iBAAiB,CA0F/E;AAMD,MAAM,WAAW,yBAAyB;IACxC,gCAAgC;IAChC,IAAI,EAAE,OAAO,CAAC;IACd,oBAAoB;IACpB,OAAO,EAAE,MAAM,IAAI,CAAC;IACpB,kDAAkD;IAClD,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAC5B,iCAAiC;IACjC,MAAM,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,KAAK,IAAI,CAAC;IAC9C,oCAAoC;IACpC,aAAa,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,IAAI,CAAC;CACrD;AAMD;;;;;;GAMG;AACH,wBAAgB,oBAAoB,CAAC,EACnC,IAAI,EACJ,OAAO,EACP,MAAM,EACN,MAAM,EACN,aAAa,GACd,EAAE,yBAAyB,qBAoB3B"}

package/dist/DashboardFilterBar.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DashboardFilterBar.d.ts","sourceRoot":"","sources":["../src/DashboardFilterBar.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH;;;;;;;;GAQG;AAEH,OAAO,KAAuC,MAAM,OAAO,CAAC;AAiB5D,OAAO,EAEL,KAAK,kBAAkB,EAExB,MAAM,iBAAiB,CAAC;AAOzB,MAAM,WAAW,uBAAuB;IACtC,IAAI,EAAE,kBAAkB,EAAE,CAAC;IAC3B,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAC5B,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,IAAI,CAAC;IAC7C,OAAO,CAAC,EAAE,MAAM,IAAI,CAAC;IACrB,UAAU,CAAC,EAAE,GAAG,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AA2ND,wBAAgB,kBAAkB,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,EAAE,uBAAuB,4BAyCrH"}
+{"version":3,"file":"DashboardFilterBar.d.ts","sourceRoot":"","sources":["../src/DashboardFilterBar.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH;;;;;;;;GAQG;AAEH,OAAO,KAAuC,MAAM,OAAO,CAAC;AAiB5D,OAAO,EAEL,KAAK,kBAAkB,EAExB,MAAM,iBAAiB,CAAC;AAoCzB,MAAM,WAAW,uBAAuB;IACtC,IAAI,EAAE,kBAAkB,EAAE,CAAC;IAC3B,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAC5B,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,IAAI,CAAC;IAC7C,OAAO,CAAC,EAAE,MAAM,IAAI,CAAC;IACrB,UAAU,CAAC,EAAE,GAAG,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAgTD,wBAAgB,kBAAkB,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,EAAE,uBAAuB,4BAyCrH"}

package/dist/DashboardGridLayout.d.ts

@@ -4,6 +4,33 @@ import * as React from 'react';
 export interface DashboardGridLayoutProps {
     schema: DashboardComponentSchema;
     className?: string;
+    /**
+     * Data-source adapter for the widgets this grid renders, handed to
+     * `DatasetWidget` for ADR-0021 dataset-bound widgets (objectui#4614).
+     *
+     * Typed `unknown`, not `any`. The sibling declares `dataSource?: any`
+     * (`DashboardRenderer.tsx:198`) for a reason that is explicitly historical —
+     * "that is precisely what it resolved to before", via the index signature that
+     * used to answer for it — and this is a NEW declaration with no prior
+     * resolution to preserve. `unknown` is what the consumer itself declares
+     * (`DatasetWidget.tsx:655`, `dataSource: unknown`), so the value is forwarded
+     * to exactly the type that receives it, and no call site is held to anything
+     * new: every value is assignable to `unknown`. Narrowing it further to a real
+     * adapter type is a separate change with its own consumer sweep, on both
+     * surfaces at once.
+     *
+     * Optional, and the omitted case is a SUPPORTED one rather than an oversight:
+     * `dashboard-grid`'s SDUI registration declares only `title` / `className`
+     * inputs, so schema-driven hosts render this component with no adapter at all.
+     * A dataset-bound widget arriving that way renders `DatasetWidget`'s own
+     * no-capability diagnostic — a visible state, never a blank tile.
+     *
+     * `SchemaRenderer` forwards this as a React prop (its `...props` spread, last:
+     * `SchemaRenderer.tsx:632`). It cannot be shadowed by the spec's per-element
+     * `dataSource` BINDING, which is stripped from the schema before that spread
+     * for exactly this reason (`SchemaRenderer.tsx:564-575`, objectstack#5576).
+     */
+    dataSource?: unknown;
     /**
      * Fires on every drag/resize tick with the raw react-grid-layout payload.
      * Useful for live previews; NOT a persistence hook.

package/dist/DashboardGridLayout.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DashboardGridLayout.d.ts","sourceRoot":"","sources":["../src/DashboardGridLayout.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAC/B,OAAO,EAA2C,KAAK,UAAU,IAAI,SAAS,EAAuC,MAAM,mBAAmB,CAAC;AAC/I,OAAO,kCAAkC,CAAC;AAI1C,OAAO,KAAK,EAAE,wBAAwB,EAAyB,MAAM,kBAAkB,CAAC;AA4BxF,MAAM,WAAW,wBAAwB;IACvC,MAAM,EAAE,wBAAwB,CAAC;IACjC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;OAGG;IACH,cAAc,CAAC,EAAE,CAAC,MAAM,EAAE,SAAS,EAAE,KAAK,IAAI,CAAC;IAC/C;;;;;;;;;OASG;IACH,cAAc,CAAC,EAAE,CAAC,MAAM,EAAE,wBAAwB,KAAK,IAAI,CAAC;IAC5D,4EAA4E;IAC5E,SAAS,CAAC,EAAE,MAAM,IAAI,CAAC;CACxB;AAED,iFAAiF;AACjF,wBAAgB,qBAAqB,CACnC,MAAM,EAAE,wBAAwB,EAChC,MAAM,EAAE,SAAS,EAAE,GAClB,wBAAwB,CAa1B;AAcD,eAAO,MAAM,mBAAmB,EAAE,KAAK,CAAC,EAAE,CAAC,wBAAwB,CA6UlE,CAAC"}
+{"version":3,"file":"DashboardGridLayout.d.ts","sourceRoot":"","sources":["../src/DashboardGridLayout.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAC/B,OAAO,EAA2C,KAAK,UAAU,IAAI,SAAS,EAAuC,MAAM,mBAAmB,CAAC;AAC/I,OAAO,kCAAkC,CAAC;AAK1C,OAAO,KAAK,EAAc,wBAAwB,EAAyB,MAAM,kBAAkB,CAAC;AA8BpG,MAAM,WAAW,wBAAwB;IACvC,MAAM,EAAE,wBAAwB,CAAC;IACjC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;;;;;;;;;;;;;;;;;;;;;;OAyBG;IACH,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB;;;OAGG;IACH,cAAc,CAAC,EAAE,CAAC,MAAM,EAAE,SAAS,EAAE,KAAK,IAAI,CAAC;IAC/C;;;;;;;;;OASG;IACH,cAAc,CAAC,EAAE,CAAC,MAAM,EAAE,wBAAwB,KAAK,IAAI,CAAC;IAC5D,4EAA4E;IAC5E,SAAS,CAAC,EAAE,MAAM,IAAI,CAAC;CACxB;AAED,iFAAiF;AACjF,wBAAgB,qBAAqB,CACnC,MAAM,EAAE,wBAAwB,EAChC,MAAM,EAAE,SAAS,EAAE,GAClB,wBAAwB,CAa1B;AAcD,eAAO,MAAM,mBAAmB,EAAE,KAAK,CAAC,EAAE,CAAC,wBAAwB,CA+blE,CAAC"}

package/dist/DashboardRenderer.d.ts

@@ -1,8 +1,51 @@
 import { DashboardComponentSchema, DashboardWidgetSchema } from '@object-ui/types';
-import { ActionDef, ActionResult, ActionContext, ModalHandler } from '@object-ui/core';
-export interface DashboardRendererProps {
+import { ActionDef, ActionResult, ActionContext, ModalHandler, SduiDomPassThroughKey } from '@object-ui/core';
+import { HTMLAttributes } from 'react';
+/**
+ * The dashboard renderer's props.
+ *
+ * ## Why there is no `[key: string]: any` here (objectui#4528)
+ *
+ * There used to be one, and it erased this entire interface. A string index
+ * signature puts `string` into `keyof Props`, so `'ref' extends keyof Props` is
+ * always true and React's `PropsWithoutRef` takes its `Omit` branch —  and
+ * `Omit` over a type carrying a string index signature keeps ONLY the index
+ * signature. Every declared property above was dropped from the resolved type:
+ * `keyof React.ComponentProps< typeof DashboardRenderer >` measured as
+ * `string | number`, and `onWidgetClick` measured as `any` at every JSX call
+ * site, while this interface went on declaring
+ * `(widgetId: string | null) => void`. The declaration was right and no
+ * consumer was held to it — a prop typo or a wrong-arity handler type-checked.
+ *
+ * The same trap, in `packages/components`, is objectui#4422 / PR #4438; this is
+ * the sweep of the two packages that issue left unswept.
+ *
+ * ## How the DOM pass-through survives without it
+ *
+ * `SchemaRenderer` hands this component the authored node's own keys, so the
+ * render function still collects an open rest object — but what may reach the
+ * element is decided by `toDomProps`' WHITELIST (objectui#4432), not by this
+ * type. The keys that whitelist forwards are therefore declared here BY NAME,
+ * derived from the whitelist constant itself so the two cannot drift, which is
+ * exactly what `@object-ui/core`'s `dom-props` doctrine asks for: "Deliberate
+ * DOM pass-through beyond this set stays available the objectui#4435 way —
+ * DECLARE it and forward it by name. Do not reopen the spread."
+ */
+export interface DashboardRendererProps extends Pick<HTMLAttributes<HTMLDivElement>, SduiDomPassThroughKey> {
     schema: DashboardComponentSchema;
     className?: string;
+    /**
+     * Data-source adapter for the widgets this dashboard renders.
+     *
+     * Destructured by the render function and handed to `DatasetWidget` /
+     * `SchemaRenderer`, and passed by both in-repo hosts (`DashboardView`,
+     * `DashboardPreview`) — but never declared until objectui#4528, because the
+     * index signature above was answering for it. Typed `any` deliberately: that
+     * is precisely what it resolved to before, so declaring it changes what is
+     * DECLARED without changing what any call site is held to. Narrowing it to a
+     * real adapter type is a separate change with its own consumer sweep.
+     */
+    dataSource?: any;
     /** Callback invoked when dashboard refresh is triggered (manual or auto) */
     onRefresh?: () => void;
     /** Total record count to display */
@@ -37,7 +80,6 @@ export interface DashboardRendererProps {
      * title/subtitle so we don't display them twice.
      */
     hideHeaderText?: boolean;
-    [key: string]: any;
 }
 /**
  * DashboardRenderer — the public dashboard renderer.
@@ -54,5 +96,5 @@ export interface DashboardRendererProps {
  * stay readable inside widget subtrees, and only a same-named filter shadows
  * the outer variable.
  */
-export declare const DashboardRenderer: import('react').ForwardRefExoticComponent<Omit<DashboardRendererProps, "ref"> & import('react').RefAttributes<HTMLDivElement>>;
+export declare const DashboardRenderer: import('react').ForwardRefExoticComponent<DashboardRendererProps & import('react').RefAttributes<HTMLDivElement>>;
 //# sourceMappingURL=DashboardRenderer.d.ts.map

package/dist/DashboardRenderer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DashboardRenderer.d.ts","sourceRoot":"","sources":["../src/DashboardRenderer.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAE,wBAAwB,EAAE,qBAAqB,EAAE,MAAM,kBAAkB,CAAC;AAGxF,OAAO,KAAK,EAAE,SAAS,EAAE,YAAY,EAAE,aAAa,EAAE,YAAY,EAAE,MAAM,iBAAiB,CAAC;AAsJ5F,MAAM,WAAW,sBAAsB;IACrC,MAAM,EAAE,wBAAwB,CAAC;IACjC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,4EAA4E;IAC5E,SAAS,CAAC,EAAE,MAAM,IAAI,CAAC;IACvB,oCAAoC;IACpC,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,iCAAiC;IACjC,WAAW,CAAC,EAAE;QAAE,IAAI,CAAC,EAAE,OAAO,CAAC;QAAC,MAAM,CAAC,EAAE,OAAO,CAAC;QAAC,MAAM,CAAC,EAAE,OAAO,CAAA;KAAE,CAAC;IACrE,kEAAkE;IAClE,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,gDAAgD;IAChD,gBAAgB,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACjC,uDAAuD;IACvD,aAAa,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,GAAG,IAAI,KAAK,IAAI,CAAC;IAClD;;;;;OAKG;IACH,gBAAgB,CAAC,EAAE,CAAC,OAAO,EAAE,qBAAqB,EAAE,KAAK,IAAI,CAAC;IAC9D,mGAAmG;IACnG,YAAY,CAAC,EAAE,YAAY,CAAC;IAC5B,wGAAwG;IACxG,cAAc,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,aAAa,KAAK,OAAO,CAAC,YAAY,CAAC,GAAG,YAAY,CAAC,CAAC;IACrH;;;;;OAKG;IACH,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,CAAC,GAAG,EAAE,MAAM,GAAG,GAAG,CAAC;CACpB;AAyuBD;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,iBAAiB,gIAiB7B,CAAC"}
+{"version":3,"file":"DashboardRenderer.d.ts","sourceRoot":"","sources":["../src/DashboardRenderer.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAc,wBAAwB,EAAE,qBAAqB,EAAE,MAAM,kBAAkB,CAAC;AAGpG,OAAO,KAAK,EAAE,SAAS,EAAE,YAAY,EAAE,aAAa,EAAE,YAAY,EAAE,qBAAqB,EAAE,MAAM,iBAAiB,CAAC;AAUnH,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,OAAO,CAAC;AAmI5C;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,WAAW,sBACf,SAAQ,IAAI,CAAC,cAAc,CAAC,cAAc,CAAC,EAAE,qBAAqB,CAAC;IACnE,MAAM,EAAE,wBAAwB,CAAC;IACjC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;;;;;;;OAUG;IACH,UAAU,CAAC,EAAE,GAAG,CAAC;IACjB,4EAA4E;IAC5E,SAAS,CAAC,EAAE,MAAM,IAAI,CAAC;IACvB,oCAAoC;IACpC,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,iCAAiC;IACjC,WAAW,CAAC,EAAE;QAAE,IAAI,CAAC,EAAE,OAAO,CAAC;QAAC,MAAM,CAAC,EAAE,OAAO,CAAC;QAAC,MAAM,CAAC,EAAE,OAAO,CAAA;KAAE,CAAC;IACrE,kEAAkE;IAClE,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,gDAAgD;IAChD,gBAAgB,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACjC,uDAAuD;IACvD,aAAa,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,GAAG,IAAI,KAAK,IAAI,CAAC;IAClD;;;;;OAKG;IACH,gBAAgB,CAAC,EAAE,CAAC,OAAO,EAAE,qBAAqB,EAAE,KAAK,IAAI,CAAC;IAC9D,mGAAmG;IACnG,YAAY,CAAC,EAAE,YAAY,CAAC;IAC5B,wGAAwG;IACxG,cAAc,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,aAAa,KAAK,OAAO,CAAC,YAAY,CAAC,GAAG,YAAY,CAAC,CAAC;IACrH;;;;;OAKG;IACH,cAAc,CAAC,EAAE,OAAO,CAAC;CAC1B;AAq8BD;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,iBAAiB,mHAiB7B,CAAC"}

package/dist/DashboardWithConfig.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DashboardWithConfig.d.ts","sourceRoot":"","sources":["../src/DashboardWithConfig.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAI/B,OAAO,KAAK,EAAE,wBAAwB,EAAyB,MAAM,kBAAkB,CAAC;AAKxF,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,mBAAmB,CAAC;AAMnE,MAAM,WAAW,wBAAwB;IACvC,qCAAqC;IACrC,MAAM,EAAE,wBAAwB,CAAC;IACjC,6DAA6D;IAC7D,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAC5B,6DAA6D;IAC7D,YAAY,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,KAAK,IAAI,CAAC;IACpD,iEAAiE;IACjE,YAAY,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,KAAK,IAAI,CAAC;IACvE,2DAA2D;IAC3D,SAAS,CAAC,EAAE,MAAM,IAAI,CAAC;IACvB,yBAAyB;IACzB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,iDAAiD;IACjD,iBAAiB,CAAC,EAAE,OAAO,CAAC;IAC5B,kDAAkD;IAClD,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;;OAKG;IACH,QAAQ,CAAC,EAAE,yBAAyB,EAAE,CAAC;IACvC,oDAAoD;IACpD,eAAe,CAAC,EAAE,OAAO,CAAC;CAC3B;AAMD;;;;;;;;;;GAUG;AACH,wBAAgB,mBAAmB,CAAC,EAClC,MAAM,EACN,MAAM,EACN,YAAY,EACZ,YAAY,EACZ,SAAS,EACT,WAAW,EACX,iBAAyB,EACzB,SAAS,EACT,QAAQ,EACR,eAAe,GAChB,EAAE,wBAAwB,qBAyJ1B"}
+{"version":3,"file":"DashboardWithConfig.d.ts","sourceRoot":"","sources":["../src/DashboardWithConfig.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAI/B,OAAO,KAAK,EAAE,wBAAwB,EAAyB,MAAM,kBAAkB,CAAC;AAKxF,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,mBAAmB,CAAC;AAMnE,MAAM,WAAW,wBAAwB;IACvC,qCAAqC;IACrC,MAAM,EAAE,wBAAwB,CAAC;IACjC,6DAA6D;IAC7D,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAC5B,6DAA6D;IAC7D,YAAY,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,KAAK,IAAI,CAAC;IACpD,iEAAiE;IACjE,YAAY,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,KAAK,IAAI,CAAC;IACvE,2DAA2D;IAC3D,SAAS,CAAC,EAAE,MAAM,IAAI,CAAC;IACvB,yBAAyB;IACzB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,iDAAiD;IACjD,iBAAiB,CAAC,EAAE,OAAO,CAAC;IAC5B,kDAAkD;IAClD,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;;OAKG;IACH,QAAQ,CAAC,EAAE,yBAAyB,EAAE,CAAC;IACvC,oDAAoD;IACpD,eAAe,CAAC,EAAE,OAAO,CAAC;CAC3B;AAMD;;;;;;;;;;GAUG;AACH,wBAAgB,mBAAmB,CAAC,EAClC,MAAM,EACN,MAAM,EACN,YAAY,EACZ,YAAY,EACZ,SAAS,EACT,WAAW,EACX,iBAAyB,EACzB,SAAS,EACT,QAAQ,EACR,eAAe,GAChB,EAAE,wBAAwB,qBAuK1B"}

package/dist/DatasetWidget.d.ts

@@ -1,4 +1,4 @@
-import { buildDatasetDrillFilter, pivotBucketId as pivotRowId, pivotCellKey } from '@object-ui/core';
+import { buildDatasetDrillFilter, pivotCellKey } from '@object-ui/core';
 /**
  * Build the record-list filter for a drilled row. Re-exported for back-compat;
  * the implementation now lives in `@object-ui/core` (`buildDatasetDrillFilter`)
@@ -10,12 +10,18 @@ export declare const buildDrillFilter: typeof buildDatasetDrillFilter;
  * live in `@object-ui/core` (`pivotBucketId` / `pivotCellKey`) so this widget
  * and the report renderer's cross-tab key their buckets identically. See that
  * module for why both are `JSON.stringify` rather than a delimiter character,
- * and for the null-placeholder residual tracked in objectstack#5666.
+ * and why an empty value encodes as JSON `null` rather than a placeholder
+ * string (objectui#4056).
  *
- * Every consumer of a row id — the cell index below AND the row-total lookup in
- * the cross-tab renderer — must build its key with these; a second, hand-rolled
- * encoding of the same id is what made the old bug invisible.
+ * Every consumer of a bucket id — the cell index below, the row-total lookup
+ * AND the column-total lookup in the cross-tab renderer — must build its key
+ * with these, over values normalized by `pivotDimensionValue`; a second,
+ * hand-rolled encoding of the same id is what made the old bug invisible.
+ *
+ * `pivotRowId` is the historical name of the axis-neutral encoder, kept as an
+ * alias so this package's published surface does not change.
  */
+declare const pivotRowId: (dimensionValues: Array<string | null>) => string;
 export { pivotRowId, pivotCellKey };
 /**
  * Pivot flat dataset rows into a cross-tab: `rowDims` go DOWN, `colDim` spreads
@@ -24,8 +30,15 @@ export { pivotRowId, pivotCellKey };
  * holding that combination's measure values. No re-aggregation — the dataset
  * already grouped by every dimension, so each cell maps to exactly one row (the
  * index is also what drill-through uses to read `drillRawRows`).
+ *
+ * `locale` is the display-locale tag the header LABELS are formatted in
+ * (objectui#4566) — this is a plain exported function, not a component, so it
+ * cannot read `useDisplayLocale()` itself. It affects `rowHeaders`/`colHeaders`
+ * only; the `id`s are opaque keys built by `pivotBucketId` from the RAW values
+ * and are deliberately untouched by it, so a locale change can never re-key a
+ * cell (which would break the `cellIndex` lookup and drill-through with it).
  */
-export declare function buildPivot(rows: Array<Record<string, unknown>>, rowDims: string[], colDim: string): {
+export declare function buildPivot(rows: Array<Record<string, unknown>>, rowDims: string[], colDim: string, locale?: string): {
     rowHeaders: Array<{
         id: string;
         labels: string[];
@@ -38,6 +51,57 @@ export declare function buildPivot(rows: Array<Record<string, unknown>>, rowDims
 };
 /** Serialize a 2D array (first row = headers) to CSV text. */
 export declare function toCsv(rows: Array<Array<string | number | null | undefined>>): string;
+/** A `DatasetSelection.timeDimensions` entry stating a bounded window. */
+export interface DatasetTimeWindow {
+    dimension: string;
+    dateRange: [string, string];
+}
+/**
+ * Split a RESOLVED runtime filter into the bounded date windows it states and
+ * the rest of the filter (objectui#3337 point 5).
+ *
+ * The executor shifts exactly one thing for a `compareTo`: a `timeDimensions`
+ * entry carrying a `dateRange`. A widget states its window in its own `filter`
+ * instead (a date macro, or the dashboard's date-range filter merged in by
+ * `DashboardRenderer`), which is why forwarding a structured `compareTo` alone
+ * still came back "compareTo needs a dated window to shift".
+ *
+ * Windows are **moved, not copied**: the comparison pass re-runs with the
+ * shifted `timeDimensions` but the SAME `runtimeFilter`, so a copy left behind
+ * would intersect the shifted window with the current one and every
+ * `<measure>__compare` column would come back empty.
+ *
+ * Only CONJUNCTIVE positions are walked — the top level and `$and` members. A
+ * window inside `$or` / `$not` is not a window the whole query runs in, so it
+ * stays in the filter untouched.
+ *
+ * **Which dimension gets shifted is not decided here.** Every window found is
+ * lowered under the name the author wrote. Zero of them, or two, is the
+ * executor's error to raise — it names the candidates (`resolveCompareDimension`).
+ * Guessing one renderer-side would trade a loud error for a quietly wrong
+ * window, which is the failure class objectstack#5011 set out to end.
+ */
+export declare function extractDateWindows(filter: unknown): {
+    windows: DatasetTimeWindow[];
+    rest: Record<string, unknown> | undefined;
+};
+/**
+ * The authored chart CHROME and the series/axis presentation merge, both of
+ * which now live in `@object-ui/core`'s `chart-presentation` beside
+ * `buildChartSeries` — the derivation they are merged onto (objectui#4877).
+ *
+ * They were written here (#3135 → objectstack#7016 → #4229) and moved when the
+ * report renderer's embedded chart turned out to need the SAME merge over the
+ * same spec keys: `ReportChartSchema` and `ChartConfigSchema` declare one
+ * vocabulary, and a second copy of the split beside this one is precisely the
+ * duplication objectui#4389 filed as a defect. The doctrine — the two
+ * admission criteria, the data/presentation ruling, why `aria` stays
+ * unforwarded — travelled with the code; see that module's header.
+ *
+ * Re-exported under their original names so this module's public surface is
+ * unchanged.
+ */
+export { chartConfigPresentation, mergeAuthoredPresentation, type AuthoredSeriesPresentation, type MergedChartSeries, } from '@object-ui/core';
 export declare function DatasetWidget({ widget, dataSource }: {
     widget: any;
     dataSource: unknown;

package/dist/DatasetWidget.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DatasetWidget.d.ts","sourceRoot":"","sources":["../src/DatasetWidget.tsx"],"names":[],"mappings":"AA8BA,OAAO,EAUL,uBAAuB,EAQvB,aAAa,IAAI,UAAU,EAC3B,YAAY,EAGb,MAAM,iBAAiB,CAAC;AAezB;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,gCAA0B,CAAC;AAExD;;;;;;;;;;GAUG;AACH,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,CAAC;AAEpC;;;;;;;GAOG;AACH,wBAAgB,UAAU,CACxB,IAAI,EAAE,KAAK,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,EACpC,OAAO,EAAE,MAAM,EAAE,EACjB,MAAM,EAAE,MAAM,GACb;IACD,UAAU,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC,CAAC;IACpD,UAAU,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IACjD,SAAS,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAChC,CAoBA;AASD,8DAA8D;AAC9D,wBAAgB,KAAK,CAAC,IAAI,EAAE,KAAK,CAAC,KAAK,CAAC,MAAM,GAAG,MAAM,GAAG,IAAI,GAAG,SAAS,CAAC,CAAC,GAAG,MAAM,CAEpF;AAmDD,wBAAgB,aAAa,CAAC,EAAE,MAAM,EAAE,UAAU,EAAE,EAAE;IAAE,MAAM,EAAE,GAAG,CAAC;IAAC,UAAU,EAAE,OAAO,CAAA;CAAE,+BAgezF"}
+{"version":3,"file":"DatasetWidget.d.ts","sourceRoot":"","sources":["../src/DatasetWidget.tsx"],"names":[],"mappings":"AAoCA,OAAO,EAYL,uBAAuB,EAUvB,YAAY,EAkBb,MAAM,iBAAiB,CAAC;AAgBzB;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,gCAA0B,CAAC;AAExD;;;;;;;;;;;;;;;GAeG;AACH,QAAA,MAAM,UAAU,mDAAgB,CAAC;AACjC,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,CAAC;AAEpC;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,UAAU,CACxB,IAAI,EAAE,KAAK,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,EACpC,OAAO,EAAE,MAAM,EAAE,EACjB,MAAM,EAAE,MAAM,EACd,MAAM,CAAC,EAAE,MAAM,GACd;IACD,UAAU,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC,CAAC;IACpD,UAAU,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IACjD,SAAS,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAChC,CAsBA;AASD,8DAA8D;AAC9D,wBAAgB,KAAK,CAAC,IAAI,EAAE,KAAK,CAAC,KAAK,CAAC,MAAM,GAAG,MAAM,GAAG,IAAI,GAAG,SAAS,CAAC,CAAC,GAAG,MAAM,CAEpF;AA6CD,0EAA0E;AAC1E,MAAM,WAAW,iBAAiB;IAChC,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAC7B;AAuBD;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,OAAO,GAAG;IACnD,OAAO,EAAE,iBAAiB,EAAE,CAAC;IAC7B,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,CAAC;CAC3C,CA4DA;AA6CD;;;;;;;;;;;;;;;GAeG;AACH,OAAO,EACL,uBAAuB,EACvB,yBAAyB,EACzB,KAAK,0BAA0B,EAC/B,KAAK,iBAAiB,GACvB,MAAM,iBAAiB,CAAC;AAEzB,wBAAgB,aAAa,CAAC,EAAE,MAAM,EAAE,UAAU,EAAE,EAAE;IAAE,MAAM,EAAE,GAAG,CAAC;IAAC,UAAU,EAAE,OAAO,CAAA;CAAE,+BAsjCzF"}

package/dist/MetricCard.d.ts

@@ -1,17 +1,36 @@
 import { default as React } from 'react';
-export interface MetricCardProps {
-    title?: string | {
-        key?: string;
-        defaultValue?: string;
-    };
+import { I18nLabel } from '@object-ui/types';
+import { SchemaHostProps } from './schemaHostProps';
+/**
+ * DOM PASS-THROUGH (objectui#4426) — see `MetricWidget.tsx`'s interface header
+ * for the full argument; this is the same widening on the same spread, onto the
+ * same Shadcn `Card` (`div`).
+ *
+ * `title` is the one key `Omit`-ed, and the omission is the accurate contract
+ * rather than a workaround. HTML's `title` is a tooltip string; this card's
+ * `title` is its HEADING, in the `I18nLabel` vocabulary — an incompatible type,
+ * and one the component destructures out and renders into `CardTitle`, so no
+ * `title` attribute has ever reached this element. Declaring the inherited DOM
+ * `title` here would be the "declared but not delivered" failure this repo
+ * treats as first-class (objectui#3290, objectui#3222): it would type-check,
+ * read as a supported tooltip, and silently do nothing. `MetricWidget` has no
+ * such collision — its heading is `label` — so it extends the DOM attributes
+ * whole. The repo's spelling for this carve-out is `ComboboxProps`
+ * (`extends Omit<React.ButtonHTMLAttributes<HTMLButtonElement>, "value" | "onChange">`),
+ * omitted there for the same reason: the component's own contract owns the name.
+ */
+export interface MetricCardProps extends Omit<React.HTMLAttributes<HTMLDivElement>, 'title'> {
+    /**
+     * Card heading, in @objectstack/spec's `I18nLabel` vocabulary — a plain
+     * string or an inline per-locale map. See `MetricWidget.label` for why the
+     * retired `{ key, defaultValue }` form is no longer accepted (objectui#4032).
+     */
+    title?: string | I18nLabel;
     value: string | number;
     icon?: string;
     trend?: 'up' | 'down' | 'neutral';
     trendValue?: string;
-    description?: string | {
-        key?: string;
-        defaultValue?: string;
-    };
+    description?: string | I18nLabel;
     className?: string;
     /** When true, the card is in a loading state (fetching data from server). */
     loading?: boolean;
@@ -22,5 +41,5 @@ export interface MetricCardProps {
  * MetricCard - Standalone metric card component for dashboard KPIs
  * Displays a metric value with optional icon, trend indicator, and description
  */
-export declare const MetricCard: React.FC<MetricCardProps>;
+export declare const MetricCard: React.FC<MetricCardProps & SchemaHostProps>;
 //# sourceMappingURL=MetricCard.d.ts.map

package/dist/MetricCard.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"MetricCard.d.ts","sourceRoot":"","sources":["../src/MetricCard.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,MAAM,OAAO,CAAC;AAY1B,MAAM,WAAW,eAAe;IAC9B,KAAK,CAAC,EAAE,MAAM,GAAG;QAAE,GAAG,CAAC,EAAE,MAAM,CAAC;QAAC,YAAY,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IACzD,KAAK,EAAE,MAAM,GAAG,MAAM,CAAC;IACvB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,CAAC,EAAE,IAAI,GAAG,MAAM,GAAG,SAAS,CAAC;IAClC,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,WAAW,CAAC,EAAE,MAAM,GAAG;QAAE,GAAG,CAAC,EAAE,MAAM,CAAC;QAAC,YAAY,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IAC/D,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,6EAA6E;IAC7E,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,uFAAuF;IACvF,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACvB;AAED;;;GAGG;AACH,eAAO,MAAM,UAAU,EAAE,KAAK,CAAC,EAAE,CAAC,eAAe,CA+DhD,CAAC"}
+{"version":3,"file":"MetricCard.d.ts","sourceRoot":"","sources":["../src/MetricCard.tsx"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,MAAM,OAAO,CAAC;AAI1B,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,kBAAkB,CAAC;AAElD,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AAEzD;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,WAAW,eAAgB,SAAQ,IAAI,CAAC,KAAK,CAAC,cAAc,CAAC,cAAc,CAAC,EAAE,OAAO,CAAC;IAC1F;;;;OAIG;IACH,KAAK,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAC3B,KAAK,EAAE,MAAM,GAAG,MAAM,CAAC;IACvB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,CAAC,EAAE,IAAI,GAAG,MAAM,GAAG,SAAS,CAAC;IAClC,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,WAAW,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IACjC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,6EAA6E;IAC7E,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,uFAAuF;IACvF,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACvB;AAED;;;GAGG;AACH,eAAO,MAAM,UAAU,EAAE,KAAK,CAAC,EAAE,CAAC,eAAe,GAAG,eAAe,CA6ElE,CAAC"}