@umriss-ui/charts 0.15.0 → 0.34.0

package/CHANGELOG.md

@@ -1,9 +1,7 @@
 # Changes to `@umriss-ui/charts`
 
 This document describes what changes for **callers** of the package: exports,
-props, behaviour. What was worked on in the repository — rebuilds, tests,
-decisions that are invisible from outside — stands in the repository's journal
-(`docs/journal.md`) and in the specs under `.scratch/`.
+props, behaviour.
 
 **The numbers.** The middle digit rises when something is added; the last one
 when something is repaired. As long as the first digit is `0`, no number
@@ -12,6 +10,8 @@ well: **whatever changes existing behaviour stands under a heading "Changed" of
 its own**, no matter which digit rose. Whoever reads only one section before an
 upgrade reads that one.
 
+From 0.34.0 all five packages share one number: they are released together, and a package without a change of its own still gets a heading for it.
+
 **Names read forwards.** Where an entry describes a name that has since been
 renamed, it is named here as it is called today; names that were removed stand
 as they stood.
@@ -29,6 +29,46 @@ interface was still expected to move before `0.3.0`.
 
 ---
 
+## 0.34.0 – A view is set, not handed back, and one locale (Oct. 2026)
+
+From this version all five packages carry one number and are released
+together.
+
+### Changed
+
+- **Numbers, dates and times follow the wording, not the browser.** Numbers used to be formatted in `navigator.language` and time labels were fixed `en-GB`, so a German browser showed `1.204,5` on an axis under a core `Stat` reading `1,204.5`, and a German application got English month names. The wording now carries the locale as a new field `locale` - `"en-GB"` by default, `"de-DE"` in `@umriss-ui/charts/wording/de` - and every number, date and time the chart formats (ticks, tooltip, data table, what a screen reader hears) follows it. A partial wording without `locale` keeps the default; a `tickFormat` or `format` of your own still wins; the clock stays 24-hour. An application that relied on the browser's language for its numbers passes the German wording, or a wording with its own `locale`.
+
+- **`initialView` is read once, and `setView` is new.** A different `initialView` on a later render is now ignored, as React ignores a changed `defaultValue`; it used to be applied whenever its content differed from the last one handed in. To go to a view later, call the new `setView(view)` that `useChart` returns: it applies a whole view, and what the view leaves out is shown whole again. `setView` is not reported through `onViewChange`, which reports what the reader did, so two charts kept in step by `onViewChange: (v) => other.setView(v)` in both directions do not answer each other. A caller that kept the reported view in state and handed it back as `initialView` writes `setView` instead: restoring a kept view is `setView(kept)`, and the state that mirrors the chart's view becomes `view` from the hook. `Echoes`, the rule that told a view reported and handed back late from one handed in, is no longer exported.
+
+- **Ten exports and one dead member are gone.** `ruleOutlier`, `ruleRun`, `ruleTrend`, `ruleTwoOfThree`, `sigmaFromLimit`, `defaultRules`, `paretoDefaults`, `toWorkingTime`, `mapSeries` and `workingTicks` are no longer exported from the package; nothing in the library or its documentation asked a caller to import them. `ControlChart`'s `rules` prop is unchanged and still takes a `Partial<RuleOptions>`. The static `ChartScene.classTick` is removed as well. `workingCalendar`, `calendarFrom`, `toWallClock` and the other working-time helpers stay.
+
+### Fixed
+
+- **A bound without a finite value is no bound.** A limit of `Infinity` on the lower side, or `-Infinity` on the upper, counted as violated by every value; `@umriss-ui/core` already ignored such a bound, and the two now agree.
+
+---
+
+## 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

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
@@ -70,7 +75,10 @@ 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:
+no selection. The words, and with them the numbers and the dates and times of the
+axes, tooltip, data table and screen-reader text, are English (`en-GB`, 24-hour
+clock); German (`de-DE`) comes from its own subpath. The `locale` of the
+wording is the one input - the browser's language is not read:
 
 ```tsx
 import { GERMAN_CHARTS_WORDING } from "@umriss-ui/charts/wording/de";
@@ -110,9 +118,10 @@ loaded: Geist when the application has it, the system fonts otherwise.
   pans by wheel, pinch, drag and keys within its `zoomLimits`, and a 'Show
   all' button brings the whole back; the legend hides and shows a series on a
   click and shows only it on a double click. `useChart(rows, { initialView,
-  onViewChange })` takes a start and reports every change, always the whole
-  view - charts in step hand each other theirs; `setDomain`, `toggleSeries`,
-  `showOnly` and `showAllSeries` stand on what the hook hands back.
+  onViewChange })` takes a start, read once, and reports what the reader does,
+  always the whole view - charts in step send each other theirs through
+  `setView`, which is not reported; `setDomain`, `toggleSeries`, `showOnly`
+  and `showAllSeries` stand on what the hook hands back.
 * **A chart that is loading says so**, as the table does: `loading` keeps
   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).
@@ -130,11 +139,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