@umriss-ui/charts 0.3.0-rc.1 → 0.3.1

package/dist/index.d.ts

@@ -685,6 +685,17 @@ export declare interface RemovedSpan {
     readonly operatingTime: number;
 }
 
+/** Any number of CSS colours - a token, `light-dark(…)`, `var(--…)`, a
+ literal - resolved to values a canvas can draw, in the scheme that applies
+ at `root`. The same probe `resolveTheme` uses, for a canvas of a
+ neighbouring package (ADR-0022): the schedule draws its subtasks with the
+ colours of @umriss-ui/core and of its caller, not with the chart palette.
+
+ Not cached: the caller keeps the result and reads anew when
+ `subscribeTheme` tells it to. Where no resolution comes back (a DOM
+ without a style engine), a colour is given back as it stands. */
+export declare function resolveColours<K extends string>(root: Element, colours: Readonly<Record<K, string>>): Record<K, string>;
+
 export declare interface ResolvedTheme {
     colorAxis: string;
     colorGrid: string;
@@ -894,6 +905,12 @@ export declare interface StateSeriesConfig<T = unknown> extends SeriesBase<T> {
     laneTo?: number;
 }
 
+/** Subscribe to theme invalidations - a switch of `color-scheme` on the
+ document, the system's preference, or `invalidateTheme()`. The scenes of
+ the charts use it, and so does any canvas that resolved its colours with
+ `resolveColours`. Returns the unsubscribe. */
+export declare function subscribeTheme(notify: () => void): () => void;
+
 /** Step for tick candidates in wall clock time, at an intended count. Rounded up
  to the next readable step, so that no more ticks arise than wanted. Above the
  day steps it continues in whole days. */
@@ -962,6 +979,18 @@ export declare interface TooltipProps<T> {
  mark in the axis band tells the reader that time was taken out there. */
 export declare function toOperatingTime(wallClock: number, input: CalendarInput): number;
 
+/** Wall clock time → operating time, but without NaN: whatever lies in removed
+ time falls onto the seam that this span collapses onto anyway; whatever lies
+ before the first or after the last interval onto 0 or onto the whole
+ operating time respectively.
+
+ Why this exists: the materialised x values must stay ascending. Binary search
+ - for a hit as for a segment boundary - assumes that, and every comparison
+ with NaN is false, so that a search over a block of NaN silently lands on the
+ wrong point. The clamped value is a POSITION, not a statement: the point
+ itself is carried as a gap and is never drawn and never hit. */
+export declare function toOperatingTimeClamped(wallClock: number, input: CalendarInput): number;
+
 /** Operating time → wall clock time; outside [0, total] there is none.
 
  At a seam - the end of an interval which is at the same time the beginning of

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@umriss-ui/charts",
-  "version": "0.3.0-rc.1",
+  "version": "0.3.1",
   "description": "Canvas-based chart library - few chart kinds, uncompromisingly clean, high performance.",
   "license": "MIT",
   "author": "Roman Händler",
@@ -27,8 +27,7 @@
     "CHANGELOG.md"
   ],
   "publishConfig": {
-    "access": "public",
-    "tag": "next"
+    "access": "public"
   },
   "sideEffects": [
     "**/*.css"
@@ -59,7 +58,7 @@
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.3.0",
     "@umriss-ui/demo": "0.0.0",
-    "@umriss-ui/core": "0.2.0"
+    "@umriss-ui/core": "0.3.1"
   },
   "scripts": {
     "props": "node --disable-warning=ExperimentalWarning --experimental-strip-types demo/props.ts",