@object-ui/plugin-charts 17.3.0 → 17.6.0

package/README.md

@@ -120,17 +120,6 @@ By using lazy loading, the main application bundle stays lean:
 
 This results in significantly faster initial page loads for applications that don't use charts on every page.
 
-<!-- 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-charts)

package/dist/AdvancedChartImpl.d.ts

@@ -1,5 +1,6 @@
 import { ChartContainerConfig } from './ChartContainerImpl';
 import { NormalizedAxis, NormalizedSeries } from './normalizeChartSchema';
+import { ChartSegmentClickEvent } from '@object-ui/core';
 /**
  * ObjectUI
  * Copyright (c) 2024-present ObjectStack Inc.
@@ -52,14 +53,34 @@ export interface AdvancedChartImplProps {
     categoryOrder?: string[];
     /**
      * Optional drill-down click handler. Fires when a chart segment is clicked
-     * with `{ category, series, value }`. Wired for bar/horizontal-bar/line/
-     * area/pie/donut. Other chart types are no-ops in L1.
+     * with `{ category, categoryId, series, value }`. Wired for
+     * bar/horizontal-bar/line/area/pie/donut/funnel/scatter/treemap/sankey —
+     * each has its own click handler attached to its mark(s) below — and for
+     * `combo`, whose `Bar`/`Line`/`Area` marks are the same components the plain
+     * cartesian branch renders and now emit the same event with the same
+     * semantics (ruled on objectui#4692).
+     *
+     * `combo` differs from the plain cartesian branch in exactly ONE way, and
+     * deliberately: **only its marks drill.** A click on the plot surface or an
+     * axis stays silent there, where the plain branch would fall back to its
+     * axis-level answer. A combo plots several measures on one plot, so a
+     * surface click has no single series answer to give — the same reasoning
+     * objectui#4672's ruling used for the pivoted case. The plain branch keeps
+     * that fallback because its own marks share one measure, so its axis answer
+     * is either unambiguous or explicitly named by recharts.
+     *
+     * That combo drills at all is what keeps its DERIVATION from costing an
+     * interaction. The branch is reachable without authoring
+     * `chartType: 'combo'`: `effectiveChartFamily` derives it whenever a series'
+     * own family disagrees with the chart's own (see its doc comment), so giving
+     * one series of a drillable chart a different `type` used to turn that
+     * chart's drill off with nothing in the authored spec saying drill was
+     * touched. It now changes the mark and nothing else.
+     *
+     * Radar is the one remaining no-op in L1 — its branch attaches no click
+     * handler anywhere.
      */
-    onChartClick?: (event: {
-        category?: string;
-        series?: string;
-        value?: number;
-    }) => void;
+    onChartClick?: (event: ChartSegmentClickEvent) => void;
     /**
      * Spec `ChartAxis` presentation for the category axis — `format` (tick
      * formatter), `title`, `showGridLines`. Its `field` already arrived as

package/dist/ChartContainerImpl.d.ts

@@ -39,7 +39,7 @@ export type ChartContainerConfig = {
         theme: Record<keyof typeof THEMES, string>;
     });
 };
-declare function ChartContainer({ id, className, children, config, disableSettleRemount, ...props }: React.ComponentProps<"div"> & {
+declare function ChartContainer({ id, className, children, config, disableSettleRemount, style, ...props }: React.ComponentProps<"div"> & {
     config: ChartContainerConfig;
     children: React.ComponentProps<typeof ResponsiveContainer>["children"];
     /**

package/dist/ChartRenderer.d.ts

@@ -1,4 +1,5 @@
 import { default as React } from 'react';
+import { ChartSegmentClickEvent } from '@object-ui/core';
 export interface ChartBarRendererProps {
     schema: {
         type: string;
@@ -88,11 +89,7 @@ export interface ChartRendererProps {
         isAnimationActive?: boolean;
     };
     /** Drill-down click handler — wired by ObjectChart when drillDown is enabled. */
-    onChartClick?: (event: {
-        category?: string;
-        series?: string;
-        value?: number;
-    }) => void;
+    onChartClick?: (event: ChartSegmentClickEvent) => void;
 }
 /**
  * ChartRenderer - The public API for the advanced chart component

package/dist/ObjectChart.d.ts

@@ -1,9 +1,19 @@
 import { default as React } from 'react';
+import { humanizeLabel } from '@object-ui/core';
 /**
  * Humanize a snake_case or kebab-case string into Title Case.
- * Local implementation to avoid a dependency on @object-ui/fields.
+ *
+ * Was a local implementation here "to avoid a dependency on
+ * `@object-ui/fields`" — byte-identical to that package's export, which
+ * `plugin-grid` / `plugin-gantt` / `plugin-detail` read, so the two could drift
+ * into a live disagreement (one dashboard can hold a chart and a grid over the
+ * same stored value). objectui#5444 moved the single implementation to
+ * `@object-ui/core`, which this package already depends on: the dependency the
+ * copy existed to avoid is still avoided, and there is now one function rather
+ * than two. Re-exported at module scope because that is the surface this file
+ * has always offered.
  */
-export declare function humanizeLabel(value: string): string;
+export { humanizeLabel };
 /**
  * The result column an object-bound `aggregate` projects its value under
  * (framework#3701, `chartAggregateValueKey` in `@objectstack/spec/ui`).
@@ -46,3 +56,16 @@ export declare function aggregateRecords(records: any[], aggregate: {
 export declare function resolveGroupByLabels(data: any[], groupByField: string, objectSchema: any, dataSource?: any, translateOption?: (value: string, fallbackLabel: string) => string): Promise<any[]>;
 export { extractRecords } from '@object-ui/core';
 export declare const ObjectChart: (props: any) => React.JSX.Element;
+/**
+ * Registry shell for `object-chart` — maps the spec's
+ * `PageComponentSchema.dataSource` binding onto the keys {@link ObjectChart}
+ * reads (objectstack#6953).
+ *
+ * Nothing used to map `dataSource.object` onto `objectName`, and this block gates
+ * BOTH its fetch and its loading state on that key (`!schema.objectName &&
+ * !schema.dataset` returns early) — so a chart authored with the binding the
+ * spec documents rendered an empty frame with no error and no request. Lives
+ * here, beside the registration, rather than in `ChartContainerImpl` — the
+ * binding is a registry-boundary concern, not a rendering one.
+ */
+export declare const ObjectChartBlock: (props: any) => React.JSX.Element;

package/dist/index.d.ts

@@ -1,7 +1,9 @@
 import { ChartBarRenderer, ChartRenderer } from './ChartRenderer';
 export type { BarChartSchema } from './types';
 export { ChartBarRenderer, ChartRenderer };
-export { ObjectChart } from './ObjectChart';
+export { ObjectChart, ObjectChartBlock } from './ObjectChart';
+export { normalizeChartSchema } from './normalizeChartSchema';
+export type { NormalizedChartSchema } from './normalizeChartSchema';
 export declare const chartComponents: {
     'bar-chart': import('react').FC<import('./ChartRenderer').ChartBarRendererProps>;
     chart: import('react').FC<import('./ChartRenderer').ChartRendererProps>;