@texturehq/edges 1.35.2 → 1.36.0

package/dist/{colors-HFXagXDT.d.cts → colors-DlH6URGg.d.cts}

@@ -211,10 +211,24 @@ interface TooltipData {
     isEvent?: boolean;
     /** Optional event metadata to display */
     eventMetadata?: Record<string, string | number>;
+    /** Optional list of event items to display in event tooltips. */
+    eventItems?: TooltipEventItem[];
+}
+interface TooltipEventItem {
+    label: string;
+    color: string;
+    metadata?: Record<string, string | number>;
 }
 interface TooltipSeries {
     label: string;
     value: number;
+    /**
+     * Optional y-axis coordinate (in data space) where the focus highlight
+     * should be drawn for this series. Defaults to `value`. Used by stacked
+     * series where the drawn position differs from the reported value.
+     */
+    chartY?: number;
+    showMarker?: boolean;
     color: string;
     type?: "area" | "line" | "bar" | "event";
     category?: string;
@@ -256,7 +270,37 @@ declare const useChartContext: () => ChartContextType;
 
 interface BaseDataPoint {
     xValue: Date;
+    /**
+     * The data value for this point. This is the value reported to tooltips and
+     * CSV exports, and — by default — also the y-axis coordinate where the point
+     * is drawn.
+     *
+     * For stacked or banded charts where the *drawn* position differs from the
+     * data value (e.g. each band is drawn at its cumulative stack top), set
+     * `chartYValue` on the point instead of mutating `yValue`. That keeps tooltip
+     * and export output honest while letting the chart draw the visual stack.
+     */
     yValue: number;
+    /**
+     * Optional render-only override for where to draw this point on the y-axis.
+     * When set, series components (e.g. `AreaSeries`, `LineSeries`) draw the
+     * point at `chartYValue` instead of `yValue`. Tooltip values and CSV exports
+     * continue to use `yValue`, so the user-facing number reflects the underlying
+     * data and not the stacked coordinate.
+     *
+     * Used for stacked area charts where each band's drawn y is the cumulative
+     * top of the stack, but the displayed value should be the band's own
+     * magnitude. Existing non-stacked consumers can leave this undefined and
+     * behavior is unchanged.
+     */
+    chartYValue?: number;
+    /**
+     * Optional render-only control for the tooltip focus marker. Defaults to true.
+     * Useful for zero-height stacked bands: the tooltip row should still report
+     * the zero value, but drawing a marker at the current stack baseline makes the
+     * band look active when it is not.
+     */
+    showTooltipMarker?: boolean;
     category?: string;
 }
 interface ChartMargin {

package/dist/{colors-_FKNnBIn.d.ts → colors-Dq4EZi3c.d.ts}

@@ -211,10 +211,24 @@ interface TooltipData {
     isEvent?: boolean;
     /** Optional event metadata to display */
     eventMetadata?: Record<string, string | number>;
+    /** Optional list of event items to display in event tooltips. */
+    eventItems?: TooltipEventItem[];
+}
+interface TooltipEventItem {
+    label: string;
+    color: string;
+    metadata?: Record<string, string | number>;
 }
 interface TooltipSeries {
     label: string;
     value: number;
+    /**
+     * Optional y-axis coordinate (in data space) where the focus highlight
+     * should be drawn for this series. Defaults to `value`. Used by stacked
+     * series where the drawn position differs from the reported value.
+     */
+    chartY?: number;
+    showMarker?: boolean;
     color: string;
     type?: "area" | "line" | "bar" | "event";
     category?: string;
@@ -256,7 +270,37 @@ declare const useChartContext: () => ChartContextType;
 
 interface BaseDataPoint {
     xValue: Date;
+    /**
+     * The data value for this point. This is the value reported to tooltips and
+     * CSV exports, and — by default — also the y-axis coordinate where the point
+     * is drawn.
+     *
+     * For stacked or banded charts where the *drawn* position differs from the
+     * data value (e.g. each band is drawn at its cumulative stack top), set
+     * `chartYValue` on the point instead of mutating `yValue`. That keeps tooltip
+     * and export output honest while letting the chart draw the visual stack.
+     */
     yValue: number;
+    /**
+     * Optional render-only override for where to draw this point on the y-axis.
+     * When set, series components (e.g. `AreaSeries`, `LineSeries`) draw the
+     * point at `chartYValue` instead of `yValue`. Tooltip values and CSV exports
+     * continue to use `yValue`, so the user-facing number reflects the underlying
+     * data and not the stacked coordinate.
+     *
+     * Used for stacked area charts where each band's drawn y is the cumulative
+     * top of the stack, but the displayed value should be the band's own
+     * magnitude. Existing non-stacked consumers can leave this undefined and
+     * behavior is unchanged.
+     */
+    chartYValue?: number;
+    /**
+     * Optional render-only control for the tooltip focus marker. Defaults to true.
+     * Useful for zero-height stacked bands: the tooltip row should still report
+     * the zero value, but drawing a marker at the current stack baseline makes the
+     * band look active when it is not.
+     */
+    showTooltipMarker?: boolean;
     category?: string;
 }
 interface ChartMargin {