@umriss-ui/charts 0.14.0 → 0.16.0

package/CHANGELOG.md

@@ -29,6 +29,74 @@ interface was still expected to move before `0.3.0`.
 
 ---
 
+## 0.16.0 – A stack's total in the data table (Oct. 2026)
+
+### Added
+
+- **The unit tests run against React 18.3.1 and 19 in CI**, and the charts are rendered to a string in a test (`tests-unit/ssr.test.tsx`).
+
+- **A stack's total in the data table.** The table of a stacked chart ends each
+  stack's members with a "Total" column (German "Summe"): the sum of the
+  stack's members at the row's x, written as the tooltip writes it - a
+  normalised stack's members show their shares and its total the sum of the
+  readings. A hidden member is out of the total. The charts demo shows it on
+  the Tooltip page, "Read a stack's total in the table".
+
+### Changed
+
+- **Every entry begins with `"use client";`.** The built files `dist/charts.js` and `dist/wording/de.js` start with the directive, then the stylesheet import, so a bundler that splits server from client code takes each as client code. The directive is written to the built entries only; the sources are unchanged.
+
+- **Every export is a client component.** A hook called in a Server Component now fails with React's message about a client reference, not one about `useState`.
+
+---
+
+## 0.15.0 – A chosen hit, a histogram, and zoom keys without a tooltip (Oct. 2026)
+
+### Changed
+
+- **A chart with a zoomable x axis is one tab stop even without a
+  `<Tooltip>`** (ADR-0030). Its plot is `role="application"` with the role
+  description "chart" and takes the focus, so `+`, `-`, Shift+←/→ and `0`
+  reach a keyboard. There is no Active point to walk: the arrows without Shift
+  do nothing. After a zoom or pan key the polite live region reads the span in
+  view ("From 10 to 90."); the summary names the zoom keys and not the walk's.
+  A chart with a tooltip, and one with neither, are unchanged.
+- **The summary names the labelled limits.** A chart with a `LimitLine` or
+  `LimitBand` that has a `label` adds "Limits: Objective 300 ms, Warning band
+  250 ms – 300 ms." to the text the plot is described by - each value in its own
+  axis' format, a band's two edges as one value. A limit without a label is left
+  out; a chart without labelled limits reads as before. The wording has a new
+  entry, `limitList`, so a custom `ChartsWording` needs it.
+
+### Added
+
+- **`bin()`**, the arithmetic behind a histogram: `bin(values, { width, count,
+  domain })`, or `bin(rows, value, options)`, returns rows with `from`, `to`,
+  the middle `x` and `count` for a `Bar` on a numeric x axis. The edges are on
+  the 1-2-5 grid of the ticks; a value on an edge falls into the bin that edge
+  starts, the last bin is closed, and what is not a finite number is skipped.
+  A given `domain` is taken as it is, and values outside it are left out.
+  Exports `Bin` and `BinOptions`. One example, "Count readings into a
+  histogram", on the Bar page.
+- **`<Tooltip limits />`**, off by default: the built-in tooltip adds one row
+  per labelled limit of the hit's y axis, its label and value in that axis'
+  format, and what a key reads out says the same. One example on the Tooltip
+  page.
+- **`onSelect`**, an option of `useChart(rows, { onSelect })`: a click or a tap
+  on a hit, and Enter on the Active point, call it with the hit - the
+  `TooltipHit` a custom tooltip's `render` receives, typed at the row. Once per
+  click; the end of a drag that pans does not report, a double click reports on
+  its first click and then resets the zoom as before. The chart holds no
+  selection and draws none: what is chosen is the application's state. It
+  needs a `<Tooltip>` for its hits (the development build warns without) and
+  the hit does not travel over `syncId`. Where it is given, the summary names
+  Enter; the wording has a new entry, `selectHelp`, so a custom
+  `ChartsWording` needs it. `ChartOptions` takes the row type as a parameter
+  (`ChartOptions<Z>`, default `unknown`). One example, "Choose a hit", on the
+  Tooltip page.
+
+---
+
 ## 0.14.0 – A chart reads its rows as they come (Oct. 2026)
 
 A chart takes rows as an application has them (ADR-0052). A category is a

package/README.md

@@ -16,10 +16,15 @@ lint rule over `packages/charts/src/**` holds that fast.
 pnpm add @umriss-ui/charts
 ```
 
-React 18 or 19 as a peer, and nothing else. `@umriss-ui/core` is **not** a
+React 18 or 19 as a peer, and nothing else; the unit tests run against 18.3 and
+19 in CI. `@umriss-ui/core` is **not** a
 dependency and not a peer dependency — if an application uses both packages, it
 does so because it chose to, not because this one required it (ADR-0020).
 
+Every entry, `./wording/de` included, begins with `"use client"`, the directive a framework
+with Server Components reads to treat a module as client code. No test runs
+inside such a framework: the charts are rendered to a string in a test.
+
 ## The smallest chart that runs
 
 ```tsx
@@ -66,8 +71,11 @@ the chart takes it away; a finger swiping over the chart scrolls the page.
 
 **By keyboard and screen reader**, a chart with a `<Tooltip>` is one tab stop:
 the arrows walk its values, ↑/↓ choose the series read first, and a screen
-reader hears each value once the keys rest and a summary of the whole. The
-words are English; German comes from its own subpath:
+reader hears each value once the keys rest and a summary of the whole. A chart
+with a zoomable x axis is one as well, without a tooltip: there is nothing to
+walk, and plus, minus, Shift with an arrow and 0 zoom and pan it. `onSelect` on
+`useChart` hears a click on a hit and Enter on the walked one; the chart keeps
+no selection. The words are English; German comes from its own subpath:
 
 ```tsx
 import { GERMAN_CHARTS_WORDING } from "@umriss-ui/charts/wording/de";
@@ -114,8 +122,9 @@ loaded: Geist when the application has it, the system fonts otherwise.
   and dims a course already drawn, and where there is nothing yet a
   silhouette of the chart to come shimmers in the plot (ADR-0042).
 * **The instruments**: `LimitLine` and `LimitBand`, `ControlChart` with its four
-  rule violations, `pareto()` with a collected remainder, and a working-time
-  axis that takes the empty hours out and marks every removed span.
+  rule violations, `pareto()` with a collected remainder, `bin()` for a
+  histogram, and a working-time axis that takes the empty hours out and marks
+  every removed span. `<Tooltip limits />` reads the labelled limits at a hit.
 * **The pure modules are exported**, not hidden: `assess`, `controlLimits`,
   `zones`, `violations`, `pareto`, `workingCalendar` and the rest. Whoever
   wants to draw something other than the composition offers should reach the
@@ -126,11 +135,12 @@ loaded: Geist when the application has it, the system fonts otherwise.
   [`docs/capabilities.md`](docs/capabilities.md) under "Performance" — they are
   not repeated here, so that a new measurement has one place to go.
 
-What it deliberately cannot do — animations, a log or band scale,
-horizontal bars, pie and radar — stands in the same record, with the reason,
+What it deliberately cannot do — animations, a log scale, pie, donut and
+radar — stands in the same record, with the reason,
 and across all five packages in
 [ADR-0032](../../docs/adr/0032-what-umriss-is-not.md). Stacking is not among
-them: bars and areas stack (`stack`, `normalize`).
+them: bars and areas stack (`stack`, `normalize`). Horizontal bars are the
+next kind to come (ADR-0059).
 
 ## More