@dloizides/ui-tables 1.22.0 → 1.24.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,538 +1,557 @@
1
- # Changelog
2
-
3
- ## 1.22.0
4
-
5
- **`StatusLedger` opens a row's detail inline, under the row (JOBS-INLINE-1 "Ledger run history opens under its row").**
6
-
7
- New optional `renderRowDetail(row)` + controlled `expandedRowKey` on `StatusLedger`, passed to the
8
- `DataTable` in the wide table and in both narrow "needs a look" sections, so the detail sits
9
- directly under the pressed row or card. The expanded row carries `aria-expanded`; the detail region
10
- is named by `getRowAccessibilityLabel`. `DataTable` gains `getRowDetailAccessibilityLabel` (defaults
11
- to the generic `uiTables.rowDetail`). Additive, nothing existing changes.
12
-
13
- ## 1.21.0
14
-
15
- **New `StatusLedger` (JOBS-UX-1 "Jobs page: one clear, consistent view of every job and source").**
16
-
17
- A status-first ledger built on `DataTable` + `Filters`: one sortable, filterable table at or above
18
- the breakpoint (768 by default, from `useWindowDimensions`), and a "needs a look first" feed below
19
- it (bad then warn rows on top, then the rest). Filters: free text, status, group; sort by any column
20
- with a `sortValue`, plus a 44px direction toggle. Generic row shape through accessors; every string
21
- via `labels`/`statusLabel`; tone colours from the theme (`toneColors` overrides). Also exports
22
- `StatusPill`, `RelativeTime` (tap swaps to absolute), `formatRelativeTime` and the pure
23
- `filterLedgerRows` / `sortLedgerRows` / `splitNeedsLook` helpers. Additive, nothing existing changes.
24
-
25
- ## 1.20.0
26
-
27
- **The rows-per-page menu opens above an RN-web Modal (UI-ZINDEX-SCALE-1 "Shared overlay z-index scale").**
28
-
29
- react-native-web mounts `Modal` in a body-level layer at zIndex 9999. On web the `SizeDropdown`
30
- menu portals to the body, and at zIndex 1000 it painted under an open Modal, so clicks fell through
31
- to the dialog. The menu now uses `Z_INDEX.popover` (10000, below toasts) and the sticky header uses
32
- `Z_INDEX.sticky` (2, unchanged), both from `@dloizides/design-tokens` ^1.13.0, which is now a dependency.
33
-
34
- ## 1.19.2
35
-
36
- **The pager shrinks and wraps beside a title (TABLES-MOBILE-1 "Filter bar and pager overflow at 360").**
37
-
38
- Visual QA of aml-v2 `/app/cases` at 360 measured the pager, placed beside the "Cases" title in a
39
- wrapping row, at 328px inside a 255px slot: `flex-shrink: 0`, no width cap, so Next ran to x=373
40
- and an `overflow: hidden` ancestor clipped it. `pager` and `pagerNav` now carry `flexShrink: 1`,
41
- `minWidth: 0` and `maxWidth: '100%'`, so they fit their line and their existing `flexWrap` breaks
42
- the count / Rows / Prev / Next onto further lines. Desktop is unchanged where the row fits.
43
-
44
- ## 1.19.1
45
-
46
- **The `Filters` / `FilterBar` actions cluster wraps (TABLES-MOBILE-1 "Filter bar and pager overflow at 360").**
47
-
48
- Visual QA of aml-v2 `/app/leaders` at 360 measured the actions row (Reset, Export CSV/PDF, Apply)
49
- at 431px inside a 255px bar: a nowrap row is one unbreakable flex item, so Apply rendered at x=373,
50
- off-screen. `filtersActions` now has `flexWrap: 'wrap'`, `flexShrink: 1` and `maxWidth: '100%'`,
51
- so the cluster fits its line and its buttons break onto further lines. Desktop is unchanged: where
52
- the row fits, nothing wraps. The 44px Apply / pager hit boxes shipped in 1.19.0.
53
-
54
- ## 1.19.0
55
-
56
- **Every pressable renders a 44x44 hit box (SHOWCASE-1 "Publish the UI showcase at ui.dloizides.com").**
57
-
58
- Live QA on ui.dloizides.com/tables at 360x640 measured switches at 40x20, page-size buttons at
59
- 32-39x30 and pager buttons 31px tall. `hitSlop` is inert on react-native-web, so the rendered box
60
- is the target. Pager buttons, page-size pills, the dropdown trigger and its options, filter action
61
- buttons, the select checkbox (gutter now 44px wide) and the select-all banner action now carry
62
- `minHeight`/`minWidth` of `MIN_TARGET_PX` (44). The filter `Switch` keeps its 40x20 track inside a
63
- 44x44 `Pressable` (`-switch-hit` test id); the inner Switch keeps focus and the switch role.
64
- The inert `hitSlop` props were removed.
65
-
66
- ## 1.18.0
67
-
68
- **`DataTable` rows now fade in on load — the Ant-design-like list entrance — via `@dloizides/ui-motion`.**
69
-
70
- When a `DataTable` mounts its rows (first load, and whenever the row set changes — sort / filter /
71
- page), each row now fades in with a small upward translate, staggered across the first few rows. It
72
- is a subtle polish layer, gated hard so it never becomes jank on a large page, and **entirely
73
- opt-outable** — omit nothing and the table behaves exactly as before minus the fade.
74
-
75
- ### What changed
76
-
77
- | Area | Detail |
78
- |---|---|
79
- | **New optional prop** | `animateRows?: boolean` (default **`true`**). Each row (and its expanded detail panel, if any) is wrapped in `@dloizides/ui-motion`'s `<FadeIn>`, keyed by the row key. |
80
- | **Capped stagger** | Only the first `ROW_ENTRANCE_STAGGER_CAP` (10) rows stagger, `ROW_ENTRANCE_STAGGER_STEP_MS` (30 ms) apart; every row past the cap shares the capped delay. A 100- or 5,000-row page settles in a fixed ~300 ms, **never** row-by-row. |
81
- | **Reduced-motion** | Honoured: rows render instantly, with **no wrapper node and no delay** (`FadeIn` gates too, but the wrapper is skipped entirely so the reduced-motion DOM is identical to the un-animated table). |
82
- | **No re-fade on re-render** | Each row's `<FadeIn>` is keyed by its row key, so React keeps its identity across unrelated re-renders (hover, a re-fetch that resolves to the SAME keys) — the entrance plays once per key, not on every render. A genuine row-set change (new keys) re-fades, as intended. |
83
- | **New test id** | `rowFadeTestID(tableTestID, key)` → `${tableTestID}-fade-${key}` (present only while animating), exported alongside the other row test-id helpers. |
84
-
85
- ### Backward compatibility
86
-
87
- - **MINOR, additive.** The public API gains one optional prop and one test-id helper; nothing is
88
- renamed or removed.
89
- - All existing behaviour is preserved: zebra, sticky header, mobile card-stack, row/per-cell/head/
90
- detail-panel/select-checkbox test ids, `onRowPress`, bulk-select, keyboard navigation, the pager,
91
- and the refetch-does-not-blank-the-grid guard.
92
- - Pass `animateRows={false}` (or run under `prefers-reduced-motion`) and rows render with no
93
- wrapper node — DOM identical to before this release.
94
- - New peer of the kit: `@dloizides/ui-motion` (`^1.0.1`) is added as a dependency.
95
-
96
- ## 1.16.0
97
-
98
- **The responsive card-stack now reads as a proper mobile layout — and keeps every E2E hook.**
99
-
100
- `DataTable` has always collapsed to a label:value card-stack below a breakpoint (`stackBreakpoint`),
101
- but on a phone the multi-column tables it powers (e.g. the organizer Passes table) were still hard
102
- to read, and the card-stack silently dropped test hooks a wide-viewport E2E suite relies on. This
103
- release makes the card-stack the readable, self-explanatory mobile layout it was meant to be —
104
- **with no change to the desktop grid and no broken selectors.**
105
-
106
- ### What changed
107
-
108
- | Area | Before | Now |
109
- |---|---|---|
110
- | **Default breakpoint** | `640` | `768` — the kit-wide narrow-viewport threshold, aligned with `@dloizides/ui-layout`'s `MENU_BREAKPOINT` (already the collapse point for the nav menu and tabs). `CARD_STACK_BREAKPOINT` is re-exported at the new value. |
111
- | **Card line layout** | label LEFT, value RIGHT on one `space-between` row (cramped for long values / action buttons) | each column's header sits **ABOVE** its value, both left-aligned, so the value gets the full card width |
112
- | **Per-cell test id `${row}-${colKey}`** | resolved **only** on the desktop grid | resolves in **BOTH** layouts (the card line carries the same id the desktop cell does) |
113
- | **Head test id `ui-data-table-head`** | **absent** in card-stack mode | resolves in **BOTH** layouts via a hidden, a11y-inert carrier (`display: none`, `aria-hidden`) — E2E selectors survive at every width |
114
-
115
- ### Backward compatibility
116
-
117
- - **The desktop grid is byte-for-byte unchanged.** Opt out of the card-stack entirely, at every
118
- width, with `stackBreakpoint={0}` (unchanged).
119
- - A column's `render` node (badge, link, **action button**) renders identically in a card cell.
120
- - Row / per-cell / head / detail-panel / select-checkbox test ids are all preserved; the only
121
- net-new guarantee is that per-cell and head ids now ALSO resolve in the card-stack.
122
- - The one observable difference for an existing consumer is cosmetic: tables between 640px and
123
- 768px wide now show the card-stack (they showed the cramped desktop row before), and cards read
124
- vertically rather than as a `space-between` row. Both are strict readability improvements — which
125
- is what keeps this a MINOR bump.
126
-
127
- All 272 tests pass (6 added for the both-layouts test-hook contract + the vertical card layout).
128
-
129
- ## 1.15.0
130
-
131
- **A re-fetch no longer blanks the grid — the server-paged paging defect.**
132
-
133
- `DataTable` returned its full-bleed loading state whenever `loading` was true, unconditionally.
134
- On a server-paged grid that is not a cosmetic flicker, it is the paging bug: clicking **Next**
135
- replaced the table with "Loading…", so the grid visibly EMPTIED and only refilled once the next
136
- page arrived. To anyone watching — and to any assertion that samples the rows after the click —
137
- the grid appeared to page to nothing. The same applied to re-filtering and to any `reload()`.
138
-
139
- Evidence this was real and not theoretical: against the live AML v2 cases console, the API
140
- returned a correct, non-overlapping page at `skip=50`, yet the UI rendered **zero** rows after
141
- Next. The rows were being discarded by this component, not by the query.
142
-
143
- ### The rule now
144
-
145
- The state view is reserved for when there is genuinely nothing to show:
146
-
147
- | `loading` | `rows.length` | Renders |
148
- |---|---|---|
149
- | true | 0 | loading state (first load) |
150
- | false | 0 | empty state |
151
- | true | > 0 | **the existing rows** (stale for a moment), `aria-busy="true"` |
152
- | false | > 0 | the rows |
153
-
154
- Rows that already exist stay on screen and swap when the new page resolves. Because the content
155
- no longer vanishes, the in-flight fetch is announced explicitly via `aria-busy` on the table
156
- container rather than being implied by the table's destruction.
157
-
158
- **Behaviour is unchanged for every first load and every empty result**, which is what keeps this a
159
- MINOR bump. The only consumers that see a difference are those that were already passing `loading`
160
- alongside non-empty `rows` — i.e. exactly the ones that were silently blanking.
161
-
162
- All 266 pre-existing tests pass unmodified; 3 added for the retained-rows / busy / swap contract.
163
-
164
- ## 1.14.0
165
-
166
- **Campaign F2 — the private filter fields are now public, in `@dloizides/ui-forms`.**
167
-
168
- This package contained a complete, themed, a11y-wired set of form controls inside its `Filters`
169
- bar and exported NONE of them. Six portals could see them working and none could import them, so
170
- the fleet reimplemented them: **6 select implementations, 5 date fields, 2 typeaheads**. Same
171
- shape as `MultiTenancy.EntityFrameworkCore` shipping no EF Core. They now live in
172
- `@dloizides/ui-forms` 1.8.0 as `SelectControl` / `TypeaheadControl` / `DateRangeControl` /
173
- `AnchoredMenu` / `controlStyles`, and this package consumes them.
174
-
175
- **No behaviour changed. All 258 pre-existing tests pass UNMODIFIED** — including
176
- `Filters.test.tsx` (which drives every field kind through the bar), `selectAccessibleName.test.tsx`
177
- (the i18n path) and `suggest.test.ts` (now running against the moved implementation). That is the
178
- proof the move preserved behaviour rather than merely relocating it.
179
-
180
- ### What moved, and what deliberately did not
181
-
182
- The controls moved; the **schema** stayed. Each field was bound to this bar's `FilterField` types
183
- (`field: SelectFilterField`, `barTestID`, `fieldTestID`), so moving them verbatim would have
184
- dragged `FilterField`, `FilterFieldKind`, `FilterValues` and `FIELD_MIN_WIDTH` into `ui-forms` —
185
- i.e. `ui-forms` would have come to own "what a filter bar's field schema is". Wrong direction.
186
- The field files are now thin ADAPTERS mapping schema → plain props.
187
-
188
- `TextField` and `BooleanField` stayed. `ui-forms` already ships two text inputs (`ThemedTextInput`,
189
- `FormField`) and a switch row (`FormSwitch`); promoting a third of each would ADD duplicates to the
190
- package this campaign is de-duplicating. Converging onto the existing ones is right but VISIBLE
191
- (focus ring, hover border, `surfaceElevated` background, different switch-row metrics), so it
192
- belongs in the visual-QA-gated wave. Both now use the shared `controlStyles` boxes, so no metric
193
- is forked in the meantime.
194
-
195
- ### `FieldShell` is deleted
196
-
197
- The private label-wrapper fork existed only because `Field` hard-coded the 13/600 `field` label
198
- voice. `Field` 1.7.0 named both contract voices, so the bar now asks for `labelVariant="control"`
199
- — the 11/700/uppercase metrics `FieldShell` carried, verbatim. This ends the label-metric split
200
- between `Field` and `FieldShell` that caused several defects this campaign.
201
-
202
- The swap replaces the label implementation under six live portals, so it is guarded by a dedicated
203
- test (`fieldShellRetirement.test.tsx`) asserting the voice, the absence of `Field`'s 16px form
204
- rhythm, the per-kind reflow rules and the caller-override precedence. Removing `labelVariant`
205
- fails two of its five assertions — verified, not assumed.
206
-
207
- ### i18n manifests are untouched
208
-
209
- `FILTERS_I18N` and `TABLE_I18N` are unchanged, and every portal guard that binds to them keeps
210
- working. `ui-forms` never calls `t`, so the one field that resolved an i18n key —
211
- `SelectField`'s `FILTERS_I18N.selectTriggerLabel` accessible name — composes that string HERE, in
212
- the adapter, and passes the finished value down as `accessibilityLabel`. The i18n stayed with the
213
- package that owns the keys.
214
-
215
- ### Notes
216
-
217
- - New peer dependency: `@dloizides/ui-forms >= 1.8.0`, plus `@dloizides/ui-buttons >= 1.4.0`
218
- inherited through it (`ui-forms` bundles `FormActions`). All five portals consuming `ui-tables`
219
- already declare `ui-buttons ^1.4.0`, so this is a declaration of existing reality, not a new
220
- requirement.
221
- - `FilterOption` and `DateRangeValue` are now ALIASES of `ui-forms`' `ControlOption` /
222
- `DateRangeValue`. Public names unchanged; one definition instead of two structurally-identical
223
- twins free to drift.
224
- - `DEFAULT_TYPEAHEAD_MIN_CHARS` / `DEFAULT_TYPEAHEAD_MAX_SUGGESTIONS` and `suggestOptions` /
225
- `isUnmatched` are re-exported from `ui-forms`. Public API unchanged.
226
- - Inherits the `AnchoredMenu` WCAG fix from `ui-forms` 1.8.0: the selected option now carries
227
- `aria-selected`. `accessibilityState` is native-only and react-native-web ignores it, so on web
228
- the current option had been conveyed by colour and font-weight alone (WCAG 1.4.1).
229
- - `AnchoredMenu` remains one of three near-identical anchored-menu implementations, with
230
- `ui-layout`'s `InlineMenu` and this package's `SizeDropdown`. Collapsing them was out of scope.
231
- The move makes it EASIER: two of the three now sit in packages that may depend on `ui-forms`, so
232
- a future collapse has an obvious home rather than needing a new shared package first.
233
-
234
- ## 1.13.0
235
-
236
- De-fork wave W1.1: pagination logic promoted from the byte-identical `PaginatedList`
237
- twins in erevna-web and katalogos-web.
238
-
239
- ### Added
240
-
241
- - `usePagedRows(rows, { pageSize })` — client-side pagination state for an already
242
- in-memory array. Returns `pageRows`, `currentPage`, `totalPages`, `setPage`,
243
- `hasPages`, `pageSize`. No new translation keys; no action required.
244
-
245
- Promoted as a **hook, not a component**, deliberately: the app-side `PaginatedList`
246
- hard-bound a `FlatList` plus app-specific empty and loading states. Only the paging
247
- maths is genuinely shared, so only that moved — callers keep their own list renderer.
248
- For server-side paging keep using `DataTable`'s pager.
249
-
250
- ### Fixed (behaviour differs from the app-side original)
251
-
252
- - The original only clamped the page index when `totalPages > 0`, so emptying the list
253
- left a stale non-zero page behind and the next non-empty render started on the wrong
254
- page. `usePagedRows` clamps to 0 in that case.
255
- - A `pageSize` of 0 divided by zero (`Math.ceil(n / 0)` → `Infinity` pages). Now floored
256
- to 1.
257
- - `setPage` clamps out-of-range input; the original trusted the caller.
258
-
259
- ## 1.12.0
260
-
261
- Accessibility fix: controls that announced a **bare number** now say what they are. Confirmed in
262
- a real browser, the rows-per-page trigger rendered `aria-label="50"` — a screen-reader user heard
263
- the value and nothing about the control. Fixed across the whole package, plus two more instances
264
- of the same defect class found while auditing.
265
-
266
- ### ⚠️ ACTION REQUIRED — add three translation keys
267
-
268
- The new accessible names are user-facing strings, so they come from the host app's locale files.
269
- **Every consuming app must add these three keys:**
270
-
271
- | Key | Params | Suggested English |
272
- |---|---|---|
273
- | `uiTables.pager.rowsTriggerLabel` | `{{p1}}` = current page size | `Rows per page, currently {{p1}}` |
274
- | `uiTables.pager.rowsOptionLabel` | `{{p1}}` = that option's size | `Show {{p1}} rows per page` |
275
- | `uiTables.filters.selectTriggerLabel` | `{{p1}}` = field label, `{{p2}}` = selection | `{{p1}}: {{p2}}` |
276
-
277
- They are exported as `TABLE_I18N.pagerRowsTriggerLabel`, `TABLE_I18N.pagerRowsOptionLabel` and
278
- `FILTERS_I18N.selectTriggerLabel`, so an app that derives its required-key list from those maps
279
- (as zygos' guard test does) picks them up automatically.
280
-
281
- **Upgrading without adding them is safe.** Unlike the usual kit contract — where an undefined key
282
- renders as its literal dotted name, the failure that put 44 raw keys on screen in zygos — a
283
- newly-introduced ACCESSIBLE-NAME key degrades to the value it replaced (the bare number, the field
284
- label). An aria-label is invisible to sighted reviewers, so a raw key there would ship silently and
285
- hurt only screen-reader users. Until you add the keys you simply keep the old, worse names.
286
-
287
- ### Fixed
288
-
289
- - **`Pager` rows-per-page trigger** (`dropdown` variant) — was `aria-label="50"`, now
290
- "Rows per page, currently 50".
291
- - **`Pager` rows-per-page options** (`dropdown` variant) — was `aria-label="100"`, now
292
- "Show 100 rows per page".
293
- - **`Pager` rows-per-page pills** (the **DEFAULT** `pills` variant) — carried the identical
294
- bare-number defect and was NOT in the original report, so it affected more consumers than the
295
- dropdown did. Same fix, same key.
296
- - **`Filters` select trigger** — `accessibilityLabel` replaces the trigger's visible text for a
297
- screen reader, so labelling it `field.label` alone silently hid the current selection: sighted
298
- users saw "Closed", screen-reader users heard only "Status". Now "Status: Closed".
299
- - **`StatCard`** — its two translation keys were string literals inlined in the component rather
300
- than members of an exported map, so an app deriving its required-key list from `TABLE_I18N`
301
- could not see them and would render them raw. Now exported as `TABLE_I18N.statCardLabel` /
302
- `TABLE_I18N.statHint`. **The key strings are unchanged** (`analytics.statCardLabel`,
303
- `analytics.statHint`) — renaming them would have broken every app that already defines them.
304
-
305
- ### Added
306
-
307
- - **`accessibleName(translated, key, fallback)`** — the internal degradation guard described
308
- above. Not exported; the kit's fallback-free i18n contract is unchanged for visible copy.
309
-
310
- Additive and backward compatible for consumers — no public prop changed, so a MINOR bump.
311
- `SizeDropdown`'s props gained `triggerLabel` / `getOptionLabel`, but that component is internal
312
- (never exported from the package root).
313
-
314
- ## 1.11.0
315
-
316
- Additive: a **declarative `Filters` bar** + **Pager** enhancements. Every change is additive and
317
- backward compatible — existing `FilterBar` / `Pager` / `DataTable` consumers (aml-v2, agora,
318
- zygos, kefi, erevna, katalogos) are untouched and every new prop is optional, so a MINOR bump.
319
- No app is migrated by this release; adoption is a later wave (see `ADOPTION.md`).
320
-
321
- - **`Filters`** — the declarative, configurable filter bar built ON the existing `FilterBar`
322
- shell (reusing its live results count + WCAG live region + actions slot). A caller passes a
323
- `fields` schema — the SUPERSET harvested from every portal's hand-rolled filters — of kinds
324
- `select` / `text` / `number` / `dateRange` / `typeahead` / `boolean`, plus a value map and
325
- `onChange`. Two value models: **LIVE** (edits apply immediately — agora, zygos) and
326
- **DRAFT/APPLY** (edits accumulate in a draft, an Apply button + Enter-in-a-field commit it —
327
- aml, kefi audit), the latter driven by the new `useFilterDraft` hook. Customisation is style
328
- (theme) + slots only: every label/option/placeholder/error is a pre-localized string; no
329
- FM/router/store. Apps can inject `@dloizides/ui-layout`'s `ModalDropdown` for the `select`
330
- field via `renderSelect` (the in-tree dropdown is the dependency-free default).
331
- - **`useFilterDraft`** — the draft-vs-applied state engine (draft + committed + `apply` / `reset`
332
- / `setField` / `dirty`), with `onApply` / `onReset` callbacks the caller wires to `setPage(1)`
333
- (the universal reset-to-page-1-on-narrowing invariant, kept free of pagination coupling).
334
- - **`suggestOptions` / `isUnmatched`** — the ranked substring matcher behind the `typeahead`
335
- field (generalized from aml's `suggestCountries`), exported for reuse.
336
- - **`Pager`** — three additive props reconciling the variants across apps: `showFirstLast`
337
- (First/Last jump buttons, disabled at bounds — erevna's `PaginationControls`),
338
- `unitLabelSingular` (renders `1 result` when `total === 1` — the singularisation apps did in
339
- the FilterBar noun), and `responsive` + `stackBreakpoint` (collapse to a compact
340
- Prev/Next-only nav below the breakpoint — the mobile fallback, mirroring the DataTable
341
- card-stack). New pager test ids `ui-pager-first` / `ui-pager-last`.
342
-
343
- ## 1.10.0
344
-
345
- Additive: **bulk-select** + **keyboard navigation** on `DataTable` (ZY-08). Every new prop is
346
- optional and CONTROLLED — omit them all and the table renders exactly as it did on 1.9.2, so
347
- erevna / katalogos / kefi / agora are unaffected. Hence a MINOR bump.
348
-
349
- - **Bulk-select** — `selectedRowKeys` + `onSelectionChange` add a checkbox gutter to the
350
- header and every row. Controlled, following the `expandedRowKeys` precedent exactly: the
351
- table keeps no internal selection state, and `onSelectionChange` is the enabler (as
352
- `renderRowDetail` is for expansion). The header checkbox is genuinely tri-state
353
- (`accessibilityState.checked: 'mixed'` + `aria-checked="mixed"`), and only ever adds or
354
- removes keys belonging to the CURRENT page — off-page keys the caller holds are preserved,
355
- because the table must not drop a selection it cannot see.
356
- - **Select all matching the filter — a FLAG, never an id list.** `matchingCount` +
357
- `onSelectAllMatchingChange` add a banner once the page is fully selected and more rows
358
- match. It emits `true`/`false`; the table never enumerates the matching rows (they are on
359
- pages it never fetched, and the ZY-02 spike measured ~2–3 ms and ~16 DOM nodes per row, so
360
- materialising thousands of them is indistinguishable from an outage). Toggling a single row
361
- under the flag drops it — the operator is no longer acting on *the filter*.
362
- - **Keyboard navigation** — `keyboardNavigation` (default **off**, because giving rows a
363
- `tabIndex` changes a page's tab order) implements the ARIA grid **roving tabindex**: one tab
364
- stop for the whole grid, ↑/↓ to move (clamped, never wrapping), Home/End, Space to toggle
365
- selection, Enter to activate via the existing `onRowPress`. Keys the table does not handle
366
- are never `preventDefault`ed, so Tab and browser shortcuts keep working. When the page
367
- changes underneath it the tab stop re-homes onto the new first row rather than vanishing —
368
- without that guard the grid would become keyboard-unreachable the moment an operator paged.
369
- Web-only in effect (focus movement and key events are DOM concerns); inert on native, via
370
- the same deliberate split as the `position: 'sticky'` header.
371
- - **a11y** — `role="grid"` / `row` / `columnheader` / `cell` when navigable; `aria-selected`
372
- on rows when selectable; row checkboxes are labelled with the ROW's name, so they announce
373
- as "Instruction ABC, checkbox" rather than an anonymous "checkbox" repeated down the page.
374
- - **🔴 A selectable row's checkbox sits OUTSIDE its pressable area** — a sibling, never a
375
- descendant. A checkbox nested inside an interactive row's `Pressable` is precisely the shape
376
- the 1.9.2 fix identified as broken: the row's pointer responders CAPTURE the gesture and
377
- cancel the child's press, so the checkbox would pass a synthetic `element.click()` test and
378
- silently do nothing under a real mouse, touch or Playwright click. A selectable row is now a
379
- plain `<View>` frame holding the checkbox and a separate pressable content area.
380
- - New exports: `rowSelectTestID(tableTestID, key)`, `selectAllTestID(tableTestID)`, the
381
- `uiTables.select.*` keys on `TABLE_I18N`, and the `selectCell` / `selectBanner`
382
- `styleOverrides` slots. No existing export changed.
383
- - Internals split for clarity as the row grew three shapes: `DataTableRow`, `TableRow`,
384
- `TableHeader`, `RowCells`, plus pure `selection.ts` / `rowNav.ts` rule modules and the
385
- `useTableSelection` / `useRovingFocus` hooks. No behaviour change for existing consumers
386
- (the full 1.9.2 suite passes untouched).
387
-
388
- ## 1.9.2
389
-
390
- - **🔴 In-cell action buttons (Edit/Delete/Stop) now fire on a real pointer gesture, not just a bare
391
- synthetic click.** A NON-interactive row (no `onRowPress`) was still rendered as a `<Pressable>`.
392
- On react-native-web a `Pressable` installs pointer responders (pointerdown/up/cancel) on the row
393
- container that CAPTURE a real mouse/touch gesture and cancel the press of any interactive child in
394
- a cell — so a Delete/Stop/Edit button inside a static row looked clickable, fired on a bare
395
- `element.click()`, but silently did nothing on an actual click/tap (and on a Playwright `.click()`,
396
- which is why the AML v2 settings webhook-delete + stop-monitoring E2Es were red). A non-pressable
397
- row is now a plain `<View>` (new `RowContainer`), so its cell controls receive the full gesture.
398
- Interactive tables (`onRowPress`) are unchanged. Same class as the earlier `disabled`→
399
- `pointer-events:none` fix; this closes the remaining pointer-responder-capture path.
400
-
401
- ## 1.9.0
402
-
403
- - **`Pager` dropdown-variant rows menu now escapes ancestor stacking contexts (web).** The
404
- `rowsVariant="dropdown"` `SizeDropdown` menu opened but painted UNDER the results table on wide
405
- web: react-native-web renders every `View` as `position: relative; z-index: 0`, so the in-tree
406
- `position: absolute; zIndex: 1000` menu was trapped inside its anchor's stacking context and lost
407
- to later-painting siblings (the table / cards below).
408
- - On **web** the open menu now renders in a PORTAL to `document.body` with `position: fixed` at the
409
- trigger's measured viewport rect (right-aligned, recomputed on scroll/resize) and a high `zIndex`
410
- — clipped by nothing, above everything. Mirrors `@dloizides/ui-layout`'s InlineMenu fix.
411
- - On **native** the menu is unchanged (in-tree `position: absolute` + `elevation`). All web-only code
412
- (portal, `document`/`window` listeners, `position: fixed`) is guarded behind `Platform.OS === 'web'`.
413
- - Outside-click dismissal now consults BOTH the anchor and the portalled menu node.
414
- - `react-dom` is added as an **optional** peer dependency (only touched on web; every RN-web consumer
415
- already has it). No API change: the `rowsVariant="dropdown"` contract, all test ids, the compact v1
416
- look and a11y (role/aria/keyboard) are unchanged.
417
-
418
- ## 1.8.0
419
-
420
- - `Pager` gains an additive, **default-off** `rowsVariant?: 'pills' | 'dropdown'` prop.
421
- - `'pills'` (default) is unchanged — the RN-idiom row of pressable size pills. Every existing
422
- consumer (erevna / katalogos / kefi / coverage) renders byte-identically.
423
- - `'dropdown'` swaps the size pills for a compact `<select>`-like anchored dropdown matching
424
- the v1 console's "Rows" select: a bordered trigger (height-matched to the Prev/Next ghost
425
- buttons) showing the current size + a chevron, opening a popover of the `pageSizeOptions`
426
- that fires `onPageSizeChange` and closes on select / outside-click / Escape. The "Rows"
427
- caption is mixed-case (not uppercase) in this variant, matching v1's muted `.hint` label.
428
- - Self-contained: the anchored dropdown is implemented inside ui-tables (new `SizeDropdown`),
429
- reusing ui-layout's InlineMenu click-outside/Escape pattern WITHOUT taking a hard dependency
430
- on `@dloizides/ui-layout` — its ModalDropdown trigger has fixed chunky padding and no chevron,
431
- so it cannot match v1's compact select, and a low-level table primitive should not depend on
432
- a higher-level layout package. New option/trigger test ids: `${testID}-size-trigger`,
433
- `${testID}-size-menu`, and the existing `${testID}-size-${size}` per option.
434
-
435
- ## 1.7.0
436
-
437
- - **Accessibility (WCAG 2.1 AA) hardening — additive + backward-compatible.**
438
- - `FilterBar`: the results-count line is now a `role="status"` / `aria-live="polite"` live
439
- region, so a screen reader announces the new count when filters change the result set
440
- (WCAG 4.1.3).
441
- - `Pager`: the Prev/Next controls and the rows-per-page pills gain a vertical `hitSlop` so the
442
- touch target reaches ~44px WITHOUT changing the rendered size (adjacent pills never overlap).
443
-
444
- ## 1.6.0
445
-
446
- - `DataTable` gains a **web row-hover highlight** on clickable rows, matching the v1 console's
447
- `.ui-table tr.clickable:hover` rule. Only interactive rows (those with an `onRowPress`) tint
448
- on hover — static rows never light up. The tint is the theme's soft brand fill
449
- (`palette.primary['500']` at low alpha via the new `softBrandTint` helper), so it re-themes
450
- per tenant, falling back to a subtle surface tint when `primary` is not a plain `#rrggbb`.
451
- The hover tint wins over zebra/`rowTint` while hovered (mirroring v1's `:hover td { background }`).
452
- - **Native-safe + backward-compatible**: hover is driven by `Pressable`'s `onHoverIn`/`onHoverOut`,
453
- which are no-ops on iOS/Android, and the handlers are wired only for interactive tables — a
454
- non-interactive table renders byte-identically to before. Benefits every consumer
455
- (erevna/katalogos/kefi/aml-v2) with clickable rows.
456
-
457
- ## 1.5.0
458
-
459
- - `Pager` gains two additive, **default-off** props so a paged grid can read exactly like the
460
- v1 AML console's `.ui-pager__info` line:
461
- - `infoPrefix?: string` — an already-translated word prefixed to the count
462
- (e.g. `"Showing"` → `Showing 1–50 of 3,023 leadership terms`).
463
- - `boldNumbers?: boolean` — renders the three counts (from / to / total) in bold
464
- `colors.text`, matching v1's `.ui-pager__info b`.
465
- - **Backward-compatible**: with both props omitted the count line is byte-identical to before
466
- (the concatenated text is unchanged even with `boldNumbers` on — bold is styling only), so
467
- existing consumers (`/coverage`, aml-v2) are unaffected.
468
-
469
- ## Unreleased
470
-
471
- - **Pixel-perfect overrides** (additive, backward-compatible). The kit's defaults are
472
- opinionated but never mandatory — a consumer that must match an existing look can now
473
- do so without forking:
474
- - `DataTable` gains `styleOverrides?: DataTableStyleOverrides` (slots: `wrap`, `headRow`,
475
- `headCell`, `row`, `cell`, `numCell`, `state`, `stateText`, `rowDetail`, `card`,
476
- `cardLine`, `cardLabel`, `cardValue`).
477
- - `Pager` gains `styleOverrides?: PagerStyleOverrides` (slots: `pager`, `pagerInfo`,
478
- `pagerNav`, `pagerRowsLabel`, `sizeGroup`, `control`, `controlText`, `sizePill`,
479
- `sizePillText`).
480
- - `FilterBar` gains `styleOverrides?: FilterBarStyleOverrides` (slots: `filters`,
481
- `filtersSpacer`, `results`, `filtersActions`).
482
- - Each slot is merged **LAST** into its style array, so an override beats the base
483
- StyleSheet **and** the inline colour the component applies from `useUi().theme`
484
- (colours are never in the StyleSheet in this kit).
485
- - Documented: `stackBreakpoint={0}` disables the responsive card-stack (`width < 0` is
486
- never true), for surfaces that never had one.
487
- - Omit `styleOverrides` and every render is byte-identical to before (verified by test).
488
-
489
- - `DataTable` — **expandable rows** (additive, backward-compatible). Two new optional props:
490
- - `renderRowDetail?: (row: T) => React.ReactNode` — renders a full-width detail panel
491
- (spanning every column) directly beneath a row, between it and the next row. Works in
492
- the desktop grid *and* in the responsive card-stack.
493
- - `expandedRowKeys?: readonly string[]` — the `keyExtractor` keys of the rows currently
494
- expanded. Expansion is **controlled by the caller** (own the state, toggle from
495
- `onRowPress`); the table keeps no internal expand state and adds no chevron.
496
- - The panel gets a stable test id `${testID}-row-detail-${key}` (new helpers
497
- `rowDetailTestID(tableTestID, key)` / `rowTestID(tableTestID, key)`), is exposed to
498
- assistive tech as a labelled region (`accessibilityRole="summary"` +
499
- the new `uiTables.rowDetail` translation key), and the row it belongs to reports
500
- `aria-expanded` / `accessibilityState.expanded`.
501
- - Omit both props and the table renders exactly as before: no extra DOM node, no extra
502
- row props, no behaviour change for existing consumers.
503
- - Unblocks kefi-web's audit log (before/after JSON snapshot panel) adopting `DataTable`.
504
-
505
- ## 1.2.0
506
-
507
- - `Pager` — new optional `unitLabel?: string` prop. When supplied it appends an
508
- already-translated unit noun to the count line, e.g. `unitLabel="leadership terms"`
509
- renders `1–50 of 3,023 leadership terms` (v1 parity). Backward-compatible: when the
510
- prop is omitted (or empty) the count line stays the generic `from–to of N`,
511
- byte-identical to prior behaviour.
512
- - Test tooling — added `src/jest-dom.d.ts` so ts-jest picks up the
513
- `@testing-library/jest-dom` matcher types (`toBeDisabled`, …) when type-checking each
514
- test file (`jest.setup.ts` sits outside the `src/**` include). Fixes the `Pager` suite
515
- failing to compile under the isolated ts-jest type-check.
516
-
517
- ## 1.1.0
518
-
519
- - `DataTable` — promoted from the `/coverage` RN-web POC and hardened into the shared,
520
- tokenized grid (the `wwwroot/shared/GRID.md` contract):
521
- - per-row `testID` + `accessibilityLabel`/`accessibilityHint`, pressable rows (`onRowPress`);
522
- - all user-facing chrome routed through the UiProvider `t` (no literals) — falls back to
523
- caller-supplied `loadingLabel`/`emptyLabel`;
524
- - fixed the POC's double `col.render()` call in the desktop path (now rendered once per cell);
525
- - added the rest of the GRID.md contract: `FilterBar`, `Pager` (page-info + Prev/Next +
526
- rows-per-page), an optional `zebra` modifier, and a `stickyHeader`;
527
- - responsive label:value card-stack via `useWindowDimensions` below `stackBreakpoint`;
528
- - every colour from `@dloizides/design-tokens` via the `useUi()` theme — no hardcoded colours.
529
- - Component tests (`DataTable`, `FilterBar`, `Pager`) added.
530
-
531
- ## 1.0.0
532
-
533
- Initial release (Capability Wave C1, batch 3).
534
-
535
- - `StatCard` — extracted from the proven erevna ↔ katalogos duplication; shares the
536
- `@dloizides/ui-feedback` UI context (`useUi`).
537
- - `DataTable` / `StatGrid` intentionally NOT included yet — they exist only in kefi-web (n=1);
538
- they'll be added when a 2nd consumer appears.
1
+ # Changelog
2
+
3
+ ## 1.24.0
4
+
5
+ **`StatusLedger` floors its status and actions columns, so a row's button and status pill are never clipped (JOBS-POLISH-1 "Jobs page visual fixes").**
6
+
7
+ Every desktop cell was `flex: weight` with react-native-web's `min-width: 0`, so on a crowded row the
8
+ actions cell shrank below its button and the table wrap's `overflow: hidden` cut "Run now" in half
9
+ (63 of 100 px visible at 1024); the status pill could spill into the next cell the same way.
10
+ `DataTableColumn` gains an optional `minWidth` (px), applied to the header and body cell alike so
11
+ they stay aligned; the ledger sets 120 on status and 136 on actions. Additive.
12
+
13
+ ## 1.23.0
14
+
15
+ **A press anywhere on an interactive `DataTable` / `StatusLedger` row opens it, including on a time cell (JOBS-NOLOSS-1 "Restore everything the old Jobs page showed").**
16
+
17
+ `RelativeTime` is its own `Pressable`, so on react-native-web it claimed the press and the row's
18
+ `onRowPress` never fired: in the wide ledger only cells without a time opened the row detail. An
19
+ interactive row now publishes its press through a context; `RelativeTime` still swaps to the
20
+ absolute time and also presses its row. Outside an interactive row nothing changes.
21
+
22
+ ## 1.22.0
23
+
24
+ **`StatusLedger` opens a row's detail inline, under the row (JOBS-INLINE-1 "Ledger run history opens under its row").**
25
+
26
+ New optional `renderRowDetail(row)` + controlled `expandedRowKey` on `StatusLedger`, passed to the
27
+ `DataTable` in the wide table and in both narrow "needs a look" sections, so the detail sits
28
+ directly under the pressed row or card. The expanded row carries `aria-expanded`; the detail region
29
+ is named by `getRowAccessibilityLabel`. `DataTable` gains `getRowDetailAccessibilityLabel` (defaults
30
+ to the generic `uiTables.rowDetail`). Additive, nothing existing changes.
31
+
32
+ ## 1.21.0
33
+
34
+ **New `StatusLedger` (JOBS-UX-1 "Jobs page: one clear, consistent view of every job and source").**
35
+
36
+ A status-first ledger built on `DataTable` + `Filters`: one sortable, filterable table at or above
37
+ the breakpoint (768 by default, from `useWindowDimensions`), and a "needs a look first" feed below
38
+ it (bad then warn rows on top, then the rest). Filters: free text, status, group; sort by any column
39
+ with a `sortValue`, plus a 44px direction toggle. Generic row shape through accessors; every string
40
+ via `labels`/`statusLabel`; tone colours from the theme (`toneColors` overrides). Also exports
41
+ `StatusPill`, `RelativeTime` (tap swaps to absolute), `formatRelativeTime` and the pure
42
+ `filterLedgerRows` / `sortLedgerRows` / `splitNeedsLook` helpers. Additive, nothing existing changes.
43
+
44
+ ## 1.20.0
45
+
46
+ **The rows-per-page menu opens above an RN-web Modal (UI-ZINDEX-SCALE-1 "Shared overlay z-index scale").**
47
+
48
+ react-native-web mounts `Modal` in a body-level layer at zIndex 9999. On web the `SizeDropdown`
49
+ menu portals to the body, and at zIndex 1000 it painted under an open Modal, so clicks fell through
50
+ to the dialog. The menu now uses `Z_INDEX.popover` (10000, below toasts) and the sticky header uses
51
+ `Z_INDEX.sticky` (2, unchanged), both from `@dloizides/design-tokens` ^1.13.0, which is now a dependency.
52
+
53
+ ## 1.19.2
54
+
55
+ **The pager shrinks and wraps beside a title (TABLES-MOBILE-1 "Filter bar and pager overflow at 360").**
56
+
57
+ Visual QA of aml-v2 `/app/cases` at 360 measured the pager, placed beside the "Cases" title in a
58
+ wrapping row, at 328px inside a 255px slot: `flex-shrink: 0`, no width cap, so Next ran to x=373
59
+ and an `overflow: hidden` ancestor clipped it. `pager` and `pagerNav` now carry `flexShrink: 1`,
60
+ `minWidth: 0` and `maxWidth: '100%'`, so they fit their line and their existing `flexWrap` breaks
61
+ the count / Rows / Prev / Next onto further lines. Desktop is unchanged where the row fits.
62
+
63
+ ## 1.19.1
64
+
65
+ **The `Filters` / `FilterBar` actions cluster wraps (TABLES-MOBILE-1 "Filter bar and pager overflow at 360").**
66
+
67
+ Visual QA of aml-v2 `/app/leaders` at 360 measured the actions row (Reset, Export CSV/PDF, Apply)
68
+ at 431px inside a 255px bar: a nowrap row is one unbreakable flex item, so Apply rendered at x=373,
69
+ off-screen. `filtersActions` now has `flexWrap: 'wrap'`, `flexShrink: 1` and `maxWidth: '100%'`,
70
+ so the cluster fits its line and its buttons break onto further lines. Desktop is unchanged: where
71
+ the row fits, nothing wraps. The 44px Apply / pager hit boxes shipped in 1.19.0.
72
+
73
+ ## 1.19.0
74
+
75
+ **Every pressable renders a 44x44 hit box (SHOWCASE-1 "Publish the UI showcase at ui.dloizides.com").**
76
+
77
+ Live QA on ui.dloizides.com/tables at 360x640 measured switches at 40x20, page-size buttons at
78
+ 32-39x30 and pager buttons 31px tall. `hitSlop` is inert on react-native-web, so the rendered box
79
+ is the target. Pager buttons, page-size pills, the dropdown trigger and its options, filter action
80
+ buttons, the select checkbox (gutter now 44px wide) and the select-all banner action now carry
81
+ `minHeight`/`minWidth` of `MIN_TARGET_PX` (44). The filter `Switch` keeps its 40x20 track inside a
82
+ 44x44 `Pressable` (`-switch-hit` test id); the inner Switch keeps focus and the switch role.
83
+ The inert `hitSlop` props were removed.
84
+
85
+ ## 1.18.0
86
+
87
+ **`DataTable` rows now fade in on load — the Ant-design-like list entrance — via `@dloizides/ui-motion`.**
88
+
89
+ When a `DataTable` mounts its rows (first load, and whenever the row set changes — sort / filter /
90
+ page), each row now fades in with a small upward translate, staggered across the first few rows. It
91
+ is a subtle polish layer, gated hard so it never becomes jank on a large page, and **entirely
92
+ opt-outable** — omit nothing and the table behaves exactly as before minus the fade.
93
+
94
+ ### What changed
95
+
96
+ | Area | Detail |
97
+ |---|---|
98
+ | **New optional prop** | `animateRows?: boolean` (default **`true`**). Each row (and its expanded detail panel, if any) is wrapped in `@dloizides/ui-motion`'s `<FadeIn>`, keyed by the row key. |
99
+ | **Capped stagger** | Only the first `ROW_ENTRANCE_STAGGER_CAP` (10) rows stagger, `ROW_ENTRANCE_STAGGER_STEP_MS` (30 ms) apart; every row past the cap shares the capped delay. A 100- or 5,000-row page settles in a fixed ~300 ms, **never** row-by-row. |
100
+ | **Reduced-motion** | Honoured: rows render instantly, with **no wrapper node and no delay** (`FadeIn` gates too, but the wrapper is skipped entirely so the reduced-motion DOM is identical to the un-animated table). |
101
+ | **No re-fade on re-render** | Each row's `<FadeIn>` is keyed by its row key, so React keeps its identity across unrelated re-renders (hover, a re-fetch that resolves to the SAME keys) — the entrance plays once per key, not on every render. A genuine row-set change (new keys) re-fades, as intended. |
102
+ | **New test id** | `rowFadeTestID(tableTestID, key)` → `${tableTestID}-fade-${key}` (present only while animating), exported alongside the other row test-id helpers. |
103
+
104
+ ### Backward compatibility
105
+
106
+ - **MINOR, additive.** The public API gains one optional prop and one test-id helper; nothing is
107
+ renamed or removed.
108
+ - All existing behaviour is preserved: zebra, sticky header, mobile card-stack, row/per-cell/head/
109
+ detail-panel/select-checkbox test ids, `onRowPress`, bulk-select, keyboard navigation, the pager,
110
+ and the refetch-does-not-blank-the-grid guard.
111
+ - Pass `animateRows={false}` (or run under `prefers-reduced-motion`) and rows render with no
112
+ wrapper node — DOM identical to before this release.
113
+ - New peer of the kit: `@dloizides/ui-motion` (`^1.0.1`) is added as a dependency.
114
+
115
+ ## 1.16.0
116
+
117
+ **The responsive card-stack now reads as a proper mobile layout — and keeps every E2E hook.**
118
+
119
+ `DataTable` has always collapsed to a label:value card-stack below a breakpoint (`stackBreakpoint`),
120
+ but on a phone the multi-column tables it powers (e.g. the organizer Passes table) were still hard
121
+ to read, and the card-stack silently dropped test hooks a wide-viewport E2E suite relies on. This
122
+ release makes the card-stack the readable, self-explanatory mobile layout it was meant to be —
123
+ **with no change to the desktop grid and no broken selectors.**
124
+
125
+ ### What changed
126
+
127
+ | Area | Before | Now |
128
+ |---|---|---|
129
+ | **Default breakpoint** | `640` | `768` — the kit-wide narrow-viewport threshold, aligned with `@dloizides/ui-layout`'s `MENU_BREAKPOINT` (already the collapse point for the nav menu and tabs). `CARD_STACK_BREAKPOINT` is re-exported at the new value. |
130
+ | **Card line layout** | label LEFT, value RIGHT on one `space-between` row (cramped for long values / action buttons) | each column's header sits **ABOVE** its value, both left-aligned, so the value gets the full card width |
131
+ | **Per-cell test id `${row}-${colKey}`** | resolved **only** on the desktop grid | resolves in **BOTH** layouts (the card line carries the same id the desktop cell does) |
132
+ | **Head test id `ui-data-table-head`** | **absent** in card-stack mode | resolves in **BOTH** layouts via a hidden, a11y-inert carrier (`display: none`, `aria-hidden`) — E2E selectors survive at every width |
133
+
134
+ ### Backward compatibility
135
+
136
+ - **The desktop grid is byte-for-byte unchanged.** Opt out of the card-stack entirely, at every
137
+ width, with `stackBreakpoint={0}` (unchanged).
138
+ - A column's `render` node (badge, link, **action button**) renders identically in a card cell.
139
+ - Row / per-cell / head / detail-panel / select-checkbox test ids are all preserved; the only
140
+ net-new guarantee is that per-cell and head ids now ALSO resolve in the card-stack.
141
+ - The one observable difference for an existing consumer is cosmetic: tables between 640px and
142
+ 768px wide now show the card-stack (they showed the cramped desktop row before), and cards read
143
+ vertically rather than as a `space-between` row. Both are strict readability improvements — which
144
+ is what keeps this a MINOR bump.
145
+
146
+ All 272 tests pass (6 added for the both-layouts test-hook contract + the vertical card layout).
147
+
148
+ ## 1.15.0
149
+
150
+ **A re-fetch no longer blanks the grid — the server-paged paging defect.**
151
+
152
+ `DataTable` returned its full-bleed loading state whenever `loading` was true, unconditionally.
153
+ On a server-paged grid that is not a cosmetic flicker, it is the paging bug: clicking **Next**
154
+ replaced the table with "Loading…", so the grid visibly EMPTIED and only refilled once the next
155
+ page arrived. To anyone watching — and to any assertion that samples the rows after the click —
156
+ the grid appeared to page to nothing. The same applied to re-filtering and to any `reload()`.
157
+
158
+ Evidence this was real and not theoretical: against the live AML v2 cases console, the API
159
+ returned a correct, non-overlapping page at `skip=50`, yet the UI rendered **zero** rows after
160
+ Next. The rows were being discarded by this component, not by the query.
161
+
162
+ ### The rule now
163
+
164
+ The state view is reserved for when there is genuinely nothing to show:
165
+
166
+ | `loading` | `rows.length` | Renders |
167
+ |---|---|---|
168
+ | true | 0 | loading state (first load) |
169
+ | false | 0 | empty state |
170
+ | true | > 0 | **the existing rows** (stale for a moment), `aria-busy="true"` |
171
+ | false | > 0 | the rows |
172
+
173
+ Rows that already exist stay on screen and swap when the new page resolves. Because the content
174
+ no longer vanishes, the in-flight fetch is announced explicitly via `aria-busy` on the table
175
+ container rather than being implied by the table's destruction.
176
+
177
+ **Behaviour is unchanged for every first load and every empty result**, which is what keeps this a
178
+ MINOR bump. The only consumers that see a difference are those that were already passing `loading`
179
+ alongside non-empty `rows` — i.e. exactly the ones that were silently blanking.
180
+
181
+ All 266 pre-existing tests pass unmodified; 3 added for the retained-rows / busy / swap contract.
182
+
183
+ ## 1.14.0
184
+
185
+ **Campaign F2 — the private filter fields are now public, in `@dloizides/ui-forms`.**
186
+
187
+ This package contained a complete, themed, a11y-wired set of form controls inside its `Filters`
188
+ bar and exported NONE of them. Six portals could see them working and none could import them, so
189
+ the fleet reimplemented them: **6 select implementations, 5 date fields, 2 typeaheads**. Same
190
+ shape as `MultiTenancy.EntityFrameworkCore` shipping no EF Core. They now live in
191
+ `@dloizides/ui-forms` 1.8.0 as `SelectControl` / `TypeaheadControl` / `DateRangeControl` /
192
+ `AnchoredMenu` / `controlStyles`, and this package consumes them.
193
+
194
+ **No behaviour changed. All 258 pre-existing tests pass UNMODIFIED** — including
195
+ `Filters.test.tsx` (which drives every field kind through the bar), `selectAccessibleName.test.tsx`
196
+ (the i18n path) and `suggest.test.ts` (now running against the moved implementation). That is the
197
+ proof the move preserved behaviour rather than merely relocating it.
198
+
199
+ ### What moved, and what deliberately did not
200
+
201
+ The controls moved; the **schema** stayed. Each field was bound to this bar's `FilterField` types
202
+ (`field: SelectFilterField`, `barTestID`, `fieldTestID`), so moving them verbatim would have
203
+ dragged `FilterField`, `FilterFieldKind`, `FilterValues` and `FIELD_MIN_WIDTH` into `ui-forms` —
204
+ i.e. `ui-forms` would have come to own "what a filter bar's field schema is". Wrong direction.
205
+ The field files are now thin ADAPTERS mapping schema → plain props.
206
+
207
+ `TextField` and `BooleanField` stayed. `ui-forms` already ships two text inputs (`ThemedTextInput`,
208
+ `FormField`) and a switch row (`FormSwitch`); promoting a third of each would ADD duplicates to the
209
+ package this campaign is de-duplicating. Converging onto the existing ones is right but VISIBLE
210
+ (focus ring, hover border, `surfaceElevated` background, different switch-row metrics), so it
211
+ belongs in the visual-QA-gated wave. Both now use the shared `controlStyles` boxes, so no metric
212
+ is forked in the meantime.
213
+
214
+ ### `FieldShell` is deleted
215
+
216
+ The private label-wrapper fork existed only because `Field` hard-coded the 13/600 `field` label
217
+ voice. `Field` 1.7.0 named both contract voices, so the bar now asks for `labelVariant="control"`
218
+ — the 11/700/uppercase metrics `FieldShell` carried, verbatim. This ends the label-metric split
219
+ between `Field` and `FieldShell` that caused several defects this campaign.
220
+
221
+ The swap replaces the label implementation under six live portals, so it is guarded by a dedicated
222
+ test (`fieldShellRetirement.test.tsx`) asserting the voice, the absence of `Field`'s 16px form
223
+ rhythm, the per-kind reflow rules and the caller-override precedence. Removing `labelVariant`
224
+ fails two of its five assertions — verified, not assumed.
225
+
226
+ ### i18n manifests are untouched
227
+
228
+ `FILTERS_I18N` and `TABLE_I18N` are unchanged, and every portal guard that binds to them keeps
229
+ working. `ui-forms` never calls `t`, so the one field that resolved an i18n key —
230
+ `SelectField`'s `FILTERS_I18N.selectTriggerLabel` accessible name — composes that string HERE, in
231
+ the adapter, and passes the finished value down as `accessibilityLabel`. The i18n stayed with the
232
+ package that owns the keys.
233
+
234
+ ### Notes
235
+
236
+ - New peer dependency: `@dloizides/ui-forms >= 1.8.0`, plus `@dloizides/ui-buttons >= 1.4.0`
237
+ inherited through it (`ui-forms` bundles `FormActions`). All five portals consuming `ui-tables`
238
+ already declare `ui-buttons ^1.4.0`, so this is a declaration of existing reality, not a new
239
+ requirement.
240
+ - `FilterOption` and `DateRangeValue` are now ALIASES of `ui-forms`' `ControlOption` /
241
+ `DateRangeValue`. Public names unchanged; one definition instead of two structurally-identical
242
+ twins free to drift.
243
+ - `DEFAULT_TYPEAHEAD_MIN_CHARS` / `DEFAULT_TYPEAHEAD_MAX_SUGGESTIONS` and `suggestOptions` /
244
+ `isUnmatched` are re-exported from `ui-forms`. Public API unchanged.
245
+ - Inherits the `AnchoredMenu` WCAG fix from `ui-forms` 1.8.0: the selected option now carries
246
+ `aria-selected`. `accessibilityState` is native-only and react-native-web ignores it, so on web
247
+ the current option had been conveyed by colour and font-weight alone (WCAG 1.4.1).
248
+ - `AnchoredMenu` remains one of three near-identical anchored-menu implementations, with
249
+ `ui-layout`'s `InlineMenu` and this package's `SizeDropdown`. Collapsing them was out of scope.
250
+ The move makes it EASIER: two of the three now sit in packages that may depend on `ui-forms`, so
251
+ a future collapse has an obvious home rather than needing a new shared package first.
252
+
253
+ ## 1.13.0
254
+
255
+ De-fork wave W1.1: pagination logic promoted from the byte-identical `PaginatedList`
256
+ twins in erevna-web and katalogos-web.
257
+
258
+ ### Added
259
+
260
+ - `usePagedRows(rows, { pageSize })` — client-side pagination state for an already
261
+ in-memory array. Returns `pageRows`, `currentPage`, `totalPages`, `setPage`,
262
+ `hasPages`, `pageSize`. No new translation keys; no action required.
263
+
264
+ Promoted as a **hook, not a component**, deliberately: the app-side `PaginatedList`
265
+ hard-bound a `FlatList` plus app-specific empty and loading states. Only the paging
266
+ maths is genuinely shared, so only that moved — callers keep their own list renderer.
267
+ For server-side paging keep using `DataTable`'s pager.
268
+
269
+ ### Fixed (behaviour differs from the app-side original)
270
+
271
+ - The original only clamped the page index when `totalPages > 0`, so emptying the list
272
+ left a stale non-zero page behind and the next non-empty render started on the wrong
273
+ page. `usePagedRows` clamps to 0 in that case.
274
+ - A `pageSize` of 0 divided by zero (`Math.ceil(n / 0)` → `Infinity` pages). Now floored
275
+ to 1.
276
+ - `setPage` clamps out-of-range input; the original trusted the caller.
277
+
278
+ ## 1.12.0
279
+
280
+ Accessibility fix: controls that announced a **bare number** now say what they are. Confirmed in
281
+ a real browser, the rows-per-page trigger rendered `aria-label="50"` — a screen-reader user heard
282
+ the value and nothing about the control. Fixed across the whole package, plus two more instances
283
+ of the same defect class found while auditing.
284
+
285
+ ### ⚠️ ACTION REQUIRED — add three translation keys
286
+
287
+ The new accessible names are user-facing strings, so they come from the host app's locale files.
288
+ **Every consuming app must add these three keys:**
289
+
290
+ | Key | Params | Suggested English |
291
+ |---|---|---|
292
+ | `uiTables.pager.rowsTriggerLabel` | `{{p1}}` = current page size | `Rows per page, currently {{p1}}` |
293
+ | `uiTables.pager.rowsOptionLabel` | `{{p1}}` = that option's size | `Show {{p1}} rows per page` |
294
+ | `uiTables.filters.selectTriggerLabel` | `{{p1}}` = field label, `{{p2}}` = selection | `{{p1}}: {{p2}}` |
295
+
296
+ They are exported as `TABLE_I18N.pagerRowsTriggerLabel`, `TABLE_I18N.pagerRowsOptionLabel` and
297
+ `FILTERS_I18N.selectTriggerLabel`, so an app that derives its required-key list from those maps
298
+ (as zygos' guard test does) picks them up automatically.
299
+
300
+ **Upgrading without adding them is safe.** Unlike the usual kit contract — where an undefined key
301
+ renders as its literal dotted name, the failure that put 44 raw keys on screen in zygos — a
302
+ newly-introduced ACCESSIBLE-NAME key degrades to the value it replaced (the bare number, the field
303
+ label). An aria-label is invisible to sighted reviewers, so a raw key there would ship silently and
304
+ hurt only screen-reader users. Until you add the keys you simply keep the old, worse names.
305
+
306
+ ### Fixed
307
+
308
+ - **`Pager` rows-per-page trigger** (`dropdown` variant) — was `aria-label="50"`, now
309
+ "Rows per page, currently 50".
310
+ - **`Pager` rows-per-page options** (`dropdown` variant) — was `aria-label="100"`, now
311
+ "Show 100 rows per page".
312
+ - **`Pager` rows-per-page pills** (the **DEFAULT** `pills` variant) — carried the identical
313
+ bare-number defect and was NOT in the original report, so it affected more consumers than the
314
+ dropdown did. Same fix, same key.
315
+ - **`Filters` select trigger** — `accessibilityLabel` replaces the trigger's visible text for a
316
+ screen reader, so labelling it `field.label` alone silently hid the current selection: sighted
317
+ users saw "Closed", screen-reader users heard only "Status". Now "Status: Closed".
318
+ - **`StatCard`** — its two translation keys were string literals inlined in the component rather
319
+ than members of an exported map, so an app deriving its required-key list from `TABLE_I18N`
320
+ could not see them and would render them raw. Now exported as `TABLE_I18N.statCardLabel` /
321
+ `TABLE_I18N.statHint`. **The key strings are unchanged** (`analytics.statCardLabel`,
322
+ `analytics.statHint`) — renaming them would have broken every app that already defines them.
323
+
324
+ ### Added
325
+
326
+ - **`accessibleName(translated, key, fallback)`** — the internal degradation guard described
327
+ above. Not exported; the kit's fallback-free i18n contract is unchanged for visible copy.
328
+
329
+ Additive and backward compatible for consumers — no public prop changed, so a MINOR bump.
330
+ `SizeDropdown`'s props gained `triggerLabel` / `getOptionLabel`, but that component is internal
331
+ (never exported from the package root).
332
+
333
+ ## 1.11.0
334
+
335
+ Additive: a **declarative `Filters` bar** + **Pager** enhancements. Every change is additive and
336
+ backward compatible — existing `FilterBar` / `Pager` / `DataTable` consumers (aml-v2, agora,
337
+ zygos, kefi, erevna, katalogos) are untouched and every new prop is optional, so a MINOR bump.
338
+ No app is migrated by this release; adoption is a later wave (see `ADOPTION.md`).
339
+
340
+ - **`Filters`** — the declarative, configurable filter bar built ON the existing `FilterBar`
341
+ shell (reusing its live results count + WCAG live region + actions slot). A caller passes a
342
+ `fields` schema — the SUPERSET harvested from every portal's hand-rolled filters — of kinds
343
+ `select` / `text` / `number` / `dateRange` / `typeahead` / `boolean`, plus a value map and
344
+ `onChange`. Two value models: **LIVE** (edits apply immediately — agora, zygos) and
345
+ **DRAFT/APPLY** (edits accumulate in a draft, an Apply button + Enter-in-a-field commit it —
346
+ aml, kefi audit), the latter driven by the new `useFilterDraft` hook. Customisation is style
347
+ (theme) + slots only: every label/option/placeholder/error is a pre-localized string; no
348
+ FM/router/store. Apps can inject `@dloizides/ui-layout`'s `ModalDropdown` for the `select`
349
+ field via `renderSelect` (the in-tree dropdown is the dependency-free default).
350
+ - **`useFilterDraft`** — the draft-vs-applied state engine (draft + committed + `apply` / `reset`
351
+ / `setField` / `dirty`), with `onApply` / `onReset` callbacks the caller wires to `setPage(1)`
352
+ (the universal reset-to-page-1-on-narrowing invariant, kept free of pagination coupling).
353
+ - **`suggestOptions` / `isUnmatched`** — the ranked substring matcher behind the `typeahead`
354
+ field (generalized from aml's `suggestCountries`), exported for reuse.
355
+ - **`Pager`** — three additive props reconciling the variants across apps: `showFirstLast`
356
+ (First/Last jump buttons, disabled at bounds — erevna's `PaginationControls`),
357
+ `unitLabelSingular` (renders `1 result` when `total === 1` — the singularisation apps did in
358
+ the FilterBar noun), and `responsive` + `stackBreakpoint` (collapse to a compact
359
+ Prev/Next-only nav below the breakpoint — the mobile fallback, mirroring the DataTable
360
+ card-stack). New pager test ids `ui-pager-first` / `ui-pager-last`.
361
+
362
+ ## 1.10.0
363
+
364
+ Additive: **bulk-select** + **keyboard navigation** on `DataTable` (ZY-08). Every new prop is
365
+ optional and CONTROLLED — omit them all and the table renders exactly as it did on 1.9.2, so
366
+ erevna / katalogos / kefi / agora are unaffected. Hence a MINOR bump.
367
+
368
+ - **Bulk-select** — `selectedRowKeys` + `onSelectionChange` add a checkbox gutter to the
369
+ header and every row. Controlled, following the `expandedRowKeys` precedent exactly: the
370
+ table keeps no internal selection state, and `onSelectionChange` is the enabler (as
371
+ `renderRowDetail` is for expansion). The header checkbox is genuinely tri-state
372
+ (`accessibilityState.checked: 'mixed'` + `aria-checked="mixed"`), and only ever adds or
373
+ removes keys belonging to the CURRENT page — off-page keys the caller holds are preserved,
374
+ because the table must not drop a selection it cannot see.
375
+ - **Select all matching the filter — a FLAG, never an id list.** `matchingCount` +
376
+ `onSelectAllMatchingChange` add a banner once the page is fully selected and more rows
377
+ match. It emits `true`/`false`; the table never enumerates the matching rows (they are on
378
+ pages it never fetched, and the ZY-02 spike measured ~2–3 ms and ~16 DOM nodes per row, so
379
+ materialising thousands of them is indistinguishable from an outage). Toggling a single row
380
+ under the flag drops it — the operator is no longer acting on *the filter*.
381
+ - **Keyboard navigation** — `keyboardNavigation` (default **off**, because giving rows a
382
+ `tabIndex` changes a page's tab order) implements the ARIA grid **roving tabindex**: one tab
383
+ stop for the whole grid, ↑/↓ to move (clamped, never wrapping), Home/End, Space to toggle
384
+ selection, Enter to activate via the existing `onRowPress`. Keys the table does not handle
385
+ are never `preventDefault`ed, so Tab and browser shortcuts keep working. When the page
386
+ changes underneath it the tab stop re-homes onto the new first row rather than vanishing —
387
+ without that guard the grid would become keyboard-unreachable the moment an operator paged.
388
+ Web-only in effect (focus movement and key events are DOM concerns); inert on native, via
389
+ the same deliberate split as the `position: 'sticky'` header.
390
+ - **a11y** — `role="grid"` / `row` / `columnheader` / `cell` when navigable; `aria-selected`
391
+ on rows when selectable; row checkboxes are labelled with the ROW's name, so they announce
392
+ as "Instruction ABC, checkbox" rather than an anonymous "checkbox" repeated down the page.
393
+ - **🔴 A selectable row's checkbox sits OUTSIDE its pressable area** — a sibling, never a
394
+ descendant. A checkbox nested inside an interactive row's `Pressable` is precisely the shape
395
+ the 1.9.2 fix identified as broken: the row's pointer responders CAPTURE the gesture and
396
+ cancel the child's press, so the checkbox would pass a synthetic `element.click()` test and
397
+ silently do nothing under a real mouse, touch or Playwright click. A selectable row is now a
398
+ plain `<View>` frame holding the checkbox and a separate pressable content area.
399
+ - New exports: `rowSelectTestID(tableTestID, key)`, `selectAllTestID(tableTestID)`, the
400
+ `uiTables.select.*` keys on `TABLE_I18N`, and the `selectCell` / `selectBanner`
401
+ `styleOverrides` slots. No existing export changed.
402
+ - Internals split for clarity as the row grew three shapes: `DataTableRow`, `TableRow`,
403
+ `TableHeader`, `RowCells`, plus pure `selection.ts` / `rowNav.ts` rule modules and the
404
+ `useTableSelection` / `useRovingFocus` hooks. No behaviour change for existing consumers
405
+ (the full 1.9.2 suite passes untouched).
406
+
407
+ ## 1.9.2
408
+
409
+ - **🔴 In-cell action buttons (Edit/Delete/Stop) now fire on a real pointer gesture, not just a bare
410
+ synthetic click.** A NON-interactive row (no `onRowPress`) was still rendered as a `<Pressable>`.
411
+ On react-native-web a `Pressable` installs pointer responders (pointerdown/up/cancel) on the row
412
+ container that CAPTURE a real mouse/touch gesture and cancel the press of any interactive child in
413
+ a cell — so a Delete/Stop/Edit button inside a static row looked clickable, fired on a bare
414
+ `element.click()`, but silently did nothing on an actual click/tap (and on a Playwright `.click()`,
415
+ which is why the AML v2 settings webhook-delete + stop-monitoring E2Es were red). A non-pressable
416
+ row is now a plain `<View>` (new `RowContainer`), so its cell controls receive the full gesture.
417
+ Interactive tables (`onRowPress`) are unchanged. Same class as the earlier `disabled`→
418
+ `pointer-events:none` fix; this closes the remaining pointer-responder-capture path.
419
+
420
+ ## 1.9.0
421
+
422
+ - **`Pager` dropdown-variant rows menu now escapes ancestor stacking contexts (web).** The
423
+ `rowsVariant="dropdown"` `SizeDropdown` menu opened but painted UNDER the results table on wide
424
+ web: react-native-web renders every `View` as `position: relative; z-index: 0`, so the in-tree
425
+ `position: absolute; zIndex: 1000` menu was trapped inside its anchor's stacking context and lost
426
+ to later-painting siblings (the table / cards below).
427
+ - On **web** the open menu now renders in a PORTAL to `document.body` with `position: fixed` at the
428
+ trigger's measured viewport rect (right-aligned, recomputed on scroll/resize) and a high `zIndex`
429
+ — clipped by nothing, above everything. Mirrors `@dloizides/ui-layout`'s InlineMenu fix.
430
+ - On **native** the menu is unchanged (in-tree `position: absolute` + `elevation`). All web-only code
431
+ (portal, `document`/`window` listeners, `position: fixed`) is guarded behind `Platform.OS === 'web'`.
432
+ - Outside-click dismissal now consults BOTH the anchor and the portalled menu node.
433
+ - `react-dom` is added as an **optional** peer dependency (only touched on web; every RN-web consumer
434
+ already has it). No API change: the `rowsVariant="dropdown"` contract, all test ids, the compact v1
435
+ look and a11y (role/aria/keyboard) are unchanged.
436
+
437
+ ## 1.8.0
438
+
439
+ - `Pager` gains an additive, **default-off** `rowsVariant?: 'pills' | 'dropdown'` prop.
440
+ - `'pills'` (default) is unchanged — the RN-idiom row of pressable size pills. Every existing
441
+ consumer (erevna / katalogos / kefi / coverage) renders byte-identically.
442
+ - `'dropdown'` swaps the size pills for a compact `<select>`-like anchored dropdown matching
443
+ the v1 console's "Rows" select: a bordered trigger (height-matched to the Prev/Next ghost
444
+ buttons) showing the current size + a chevron, opening a popover of the `pageSizeOptions`
445
+ that fires `onPageSizeChange` and closes on select / outside-click / Escape. The "Rows"
446
+ caption is mixed-case (not uppercase) in this variant, matching v1's muted `.hint` label.
447
+ - Self-contained: the anchored dropdown is implemented inside ui-tables (new `SizeDropdown`),
448
+ reusing ui-layout's InlineMenu click-outside/Escape pattern WITHOUT taking a hard dependency
449
+ on `@dloizides/ui-layout` — its ModalDropdown trigger has fixed chunky padding and no chevron,
450
+ so it cannot match v1's compact select, and a low-level table primitive should not depend on
451
+ a higher-level layout package. New option/trigger test ids: `${testID}-size-trigger`,
452
+ `${testID}-size-menu`, and the existing `${testID}-size-${size}` per option.
453
+
454
+ ## 1.7.0
455
+
456
+ - **Accessibility (WCAG 2.1 AA) hardening — additive + backward-compatible.**
457
+ - `FilterBar`: the results-count line is now a `role="status"` / `aria-live="polite"` live
458
+ region, so a screen reader announces the new count when filters change the result set
459
+ (WCAG 4.1.3).
460
+ - `Pager`: the Prev/Next controls and the rows-per-page pills gain a vertical `hitSlop` so the
461
+ touch target reaches ~44px WITHOUT changing the rendered size (adjacent pills never overlap).
462
+
463
+ ## 1.6.0
464
+
465
+ - `DataTable` gains a **web row-hover highlight** on clickable rows, matching the v1 console's
466
+ `.ui-table tr.clickable:hover` rule. Only interactive rows (those with an `onRowPress`) tint
467
+ on hover — static rows never light up. The tint is the theme's soft brand fill
468
+ (`palette.primary['500']` at low alpha via the new `softBrandTint` helper), so it re-themes
469
+ per tenant, falling back to a subtle surface tint when `primary` is not a plain `#rrggbb`.
470
+ The hover tint wins over zebra/`rowTint` while hovered (mirroring v1's `:hover td { background }`).
471
+ - **Native-safe + backward-compatible**: hover is driven by `Pressable`'s `onHoverIn`/`onHoverOut`,
472
+ which are no-ops on iOS/Android, and the handlers are wired only for interactive tables — a
473
+ non-interactive table renders byte-identically to before. Benefits every consumer
474
+ (erevna/katalogos/kefi/aml-v2) with clickable rows.
475
+
476
+ ## 1.5.0
477
+
478
+ - `Pager` gains two additive, **default-off** props so a paged grid can read exactly like the
479
+ v1 AML console's `.ui-pager__info` line:
480
+ - `infoPrefix?: string` — an already-translated word prefixed to the count
481
+ (e.g. `"Showing"` → `Showing 1–50 of 3,023 leadership terms`).
482
+ - `boldNumbers?: boolean` — renders the three counts (from / to / total) in bold
483
+ `colors.text`, matching v1's `.ui-pager__info b`.
484
+ - **Backward-compatible**: with both props omitted the count line is byte-identical to before
485
+ (the concatenated text is unchanged even with `boldNumbers` on — bold is styling only), so
486
+ existing consumers (`/coverage`, aml-v2) are unaffected.
487
+
488
+ ## Unreleased
489
+
490
+ - **Pixel-perfect overrides** (additive, backward-compatible). The kit's defaults are
491
+ opinionated but never mandatory — a consumer that must match an existing look can now
492
+ do so without forking:
493
+ - `DataTable` gains `styleOverrides?: DataTableStyleOverrides` (slots: `wrap`, `headRow`,
494
+ `headCell`, `row`, `cell`, `numCell`, `state`, `stateText`, `rowDetail`, `card`,
495
+ `cardLine`, `cardLabel`, `cardValue`).
496
+ - `Pager` gains `styleOverrides?: PagerStyleOverrides` (slots: `pager`, `pagerInfo`,
497
+ `pagerNav`, `pagerRowsLabel`, `sizeGroup`, `control`, `controlText`, `sizePill`,
498
+ `sizePillText`).
499
+ - `FilterBar` gains `styleOverrides?: FilterBarStyleOverrides` (slots: `filters`,
500
+ `filtersSpacer`, `results`, `filtersActions`).
501
+ - Each slot is merged **LAST** into its style array, so an override beats the base
502
+ StyleSheet **and** the inline colour the component applies from `useUi().theme`
503
+ (colours are never in the StyleSheet in this kit).
504
+ - Documented: `stackBreakpoint={0}` disables the responsive card-stack (`width < 0` is
505
+ never true), for surfaces that never had one.
506
+ - Omit `styleOverrides` and every render is byte-identical to before (verified by test).
507
+
508
+ - `DataTable` — **expandable rows** (additive, backward-compatible). Two new optional props:
509
+ - `renderRowDetail?: (row: T) => React.ReactNode` — renders a full-width detail panel
510
+ (spanning every column) directly beneath a row, between it and the next row. Works in
511
+ the desktop grid *and* in the responsive card-stack.
512
+ - `expandedRowKeys?: readonly string[]` — the `keyExtractor` keys of the rows currently
513
+ expanded. Expansion is **controlled by the caller** (own the state, toggle from
514
+ `onRowPress`); the table keeps no internal expand state and adds no chevron.
515
+ - The panel gets a stable test id `${testID}-row-detail-${key}` (new helpers
516
+ `rowDetailTestID(tableTestID, key)` / `rowTestID(tableTestID, key)`), is exposed to
517
+ assistive tech as a labelled region (`accessibilityRole="summary"` +
518
+ the new `uiTables.rowDetail` translation key), and the row it belongs to reports
519
+ `aria-expanded` / `accessibilityState.expanded`.
520
+ - Omit both props and the table renders exactly as before: no extra DOM node, no extra
521
+ row props, no behaviour change for existing consumers.
522
+ - Unblocks kefi-web's audit log (before/after JSON snapshot panel) adopting `DataTable`.
523
+
524
+ ## 1.2.0
525
+
526
+ - `Pager` — new optional `unitLabel?: string` prop. When supplied it appends an
527
+ already-translated unit noun to the count line, e.g. `unitLabel="leadership terms"`
528
+ renders `1–50 of 3,023 leadership terms` (v1 parity). Backward-compatible: when the
529
+ prop is omitted (or empty) the count line stays the generic `from–to of N`,
530
+ byte-identical to prior behaviour.
531
+ - Test tooling — added `src/jest-dom.d.ts` so ts-jest picks up the
532
+ `@testing-library/jest-dom` matcher types (`toBeDisabled`, …) when type-checking each
533
+ test file (`jest.setup.ts` sits outside the `src/**` include). Fixes the `Pager` suite
534
+ failing to compile under the isolated ts-jest type-check.
535
+
536
+ ## 1.1.0
537
+
538
+ - `DataTable` — promoted from the `/coverage` RN-web POC and hardened into the shared,
539
+ tokenized grid (the `wwwroot/shared/GRID.md` contract):
540
+ - per-row `testID` + `accessibilityLabel`/`accessibilityHint`, pressable rows (`onRowPress`);
541
+ - all user-facing chrome routed through the UiProvider `t` (no literals) — falls back to
542
+ caller-supplied `loadingLabel`/`emptyLabel`;
543
+ - fixed the POC's double `col.render()` call in the desktop path (now rendered once per cell);
544
+ - added the rest of the GRID.md contract: `FilterBar`, `Pager` (page-info + Prev/Next +
545
+ rows-per-page), an optional `zebra` modifier, and a `stickyHeader`;
546
+ - responsive label:value card-stack via `useWindowDimensions` below `stackBreakpoint`;
547
+ - every colour from `@dloizides/design-tokens` via the `useUi()` theme — no hardcoded colours.
548
+ - Component tests (`DataTable`, `FilterBar`, `Pager`) added.
549
+
550
+ ## 1.0.0
551
+
552
+ Initial release (Capability Wave C1, batch 3).
553
+
554
+ - `StatCard` — extracted from the proven erevna ↔ katalogos duplication; shares the
555
+ `@dloizides/ui-feedback` UI context (`useUi`).
556
+ - `DataTable` / `StatGrid` intentionally NOT included yet — they exist only in kefi-web (n=1);
557
+ they'll be added when a 2nd consumer appears.