@umriss-ui/charts 0.13.0 → 0.15.0

package/CHANGELOG.md

@@ -29,6 +29,106 @@ interface was still expected to move before `0.3.0`.
 
 ---
 
+## 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
+value: `<XAxis value="costCentre" />` over rows that hold a name gives every
+distinct one a place, a tick and its label - no position computed per row, no
+`ticks` listed, no `tickFormat` that looks the name up. An instant is a value:
+a `Date`, or with `time` the ISO string an API sends. Numeric positions with
+named ticks keep working as they did; nothing is taken away.
+
+### Added
+
+- **A category on the x axis.** `XAxis value` reads a string field or a
+  function returning a string.
+  - Every distinct category gets a place, in the order the rows first bring
+    them - the series in the order they are declared, a hidden one included.
+  - The category is its label: under the tick, in the tooltip, the keyboard
+    readout, the summary and the data table.
+  - The rows may come in any order; a hit and a `value` function's `index`
+    still name your row. A row without a category is left out.
+  - The type decides, never the content: `"2024"` is a category, `2024` a
+    number. One axis has one kind; DEV names a series that brings the other.
+  - Bars stand side by side and stack, a line stands on the middle of a
+    category, zoom works in places.
+- **`categories` on `XAxis` and `YAxis`**: your own list, which is the order
+  and the extent. A category no row carries keeps its empty place; a row whose
+  category is not listed is not drawn, and DEV names it.
+- **`categoryLabel` on `XAxis` and `YAxis`**: what is written for a category
+  where the rows hold a key and not a name. Two categories may share a label.
+- **Categories along y.** `Matrix value` reads a string field, and the y axis
+  lists a row per category; the tooltip names a cell's row. `StateBand lane`
+  names the band's lane, a category of its y axis - instead of `laneFrom` and
+  `laneTo`, which stay for a numeric axis; the compiler refuses both at once.
+  The first category stands at the top. A series of numbers on a y axis that
+  has categories is not drawn: one axis has one kind.
+- **A `Date` on the x axis** puts the axis in time without `time`.
+- **ISO 8601 strings with `time`.** A date with a time and no offset is local
+  time, a date alone is UTC - the platform's rule. A string that is no instant
+  is not drawn, and DEV names its row.
+- **A `Date` where you name a place in time**: a fixed `domain` pair on
+  `XAxis`, `value` on `LimitLine`, `from` and `to` on `LimitBand`.
+- **Types**: `AxisValue`, `AxisField`, `OneLane`.
+
+### Changed
+
+- **A category axis spans its places with half a step at either end**,
+  whatever stands on it. A line over categories therefore begins half a step
+  inside the plot, where a line over the positions 0, 1, 2 began at its edge.
+  Only an axis that reads categories is affected.
+- **`tickFormat`, `ticks` and `tickCount` do not apply to an axis that reads
+  categories**; DEV says so. They keep their job on a numeric and a time axis.
+
+---
+
 ## 0.13.0 – A chart fills its frame, never below its floor (Oct. 2026)
 
 ### Changed

package/README.md

@@ -66,8 +66,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";
@@ -97,6 +100,10 @@ loaded: Geist when the application has it, the system fonts otherwise.
 * **Seven series kinds** in one chart on shared axes: `Line`, `Area`, `Bar`,
   `BoxPlot`, `Scatter`, `StateBand`, `Matrix`. Occupancy — work on people or vehicles, idle time,
   double bookings — is `@umriss-ui/schedule`'s (ADR-0026).
+* **Rows as they come** (ADR-0052): an axis reads a category from a string -
+  a place, a tick and its name each, in the rows' order or your own
+  `categories` - and an instant from a `Date` or, with `time`, from the ISO
+  string an API sends. No position computed per row, no tick list, no lookup.
 * **Several axes per orientation**, each with its own extent; only the first
   registered axis per orientation draws a grid.
 * **The chart holds its own view** (ADR-0047): an `XAxis zoomable` zooms and
@@ -110,8 +117,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
@@ -122,7 +130,7 @@ 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 category scale,
+What it deliberately cannot do — animations, a log or band scale,
 horizontal bars, pie 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