@ids-group-ltd/ids-design-system 0.7.1 → 0.9.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.
@@ -0,0 +1,179 @@
1
+ {
2
+ "version": "0.8.0",
3
+ "items": [
4
+ {
5
+ "id": "table-client-sort-replaced-by-sort-mode",
6
+ "kind": "removed-api",
7
+ "old": "ds-table[clientSort]",
8
+ "new": "sortMode",
9
+ "note": "`ds-table`'s boolean `clientSort` is REMOVED and replaced by `sortMode: 'client' | 'server' | 'none'`. The boolean could not express \"nothing sorts\", so a column marked `sortable: true` on a table with no sorting drew a header that looked live, showed a caret on hover and did nothing — mm-broker shipped several detail tables that way and only caught it in a browser walkthrough. ACTION, mechanical: `[clientSort]=\"true\"` becomes `sortMode=\"client\"`; a bare `clientSort` attribute becomes `sortMode=\"client\"`; `[clientSort]=\"false\"` or `[clientSort]=\"expr\"` becomes `[sortMode]=\"expr ? 'client' : 'server'\"`. A table that had NO clientSort binding and reorders in its own `(sortChange)` handler must now say `sortMode=\"server\"` — this is the one case that is not a find/replace, because the DEFAULT CHANGED: unset now resolves to `'client'`, so a table that previously only emitted `sortChange` will ALSO sort its own rows unless it declares `'server'`. That default flip is deliberate — it makes `sortable: true` always do something — but for a SERVER-PAGED table (one that binds `total`) client sorting reorders the current page only, so the rows look sorted and are not; dev builds warn about exactly that combination. Tables that render a sortable column but sort nowhere should declare `sortMode=\"none\"`, which now drops the button, the caret and `aria-sort` instead of leaving a dead control. NOTE for TypeScript callers: the union is exported as `TableSortMode`, so a field, computed or method that supplies the mode to `[sortMode]` can be typed with `import type { TableSortMode } from '@ids-group-ltd/ids-design-system';` rather than repeating the literals.",
10
+ "searchHints": [
11
+ "clientSort",
12
+ "[clientSort]",
13
+ "sortChange",
14
+ "(sortChange)",
15
+ "sortable: true",
16
+ "TableColumn",
17
+ "ds-table"
18
+ ]
19
+ },
20
+ {
21
+ "id": "exported-class-members-grew",
22
+ "kind": "behavior",
23
+ "old": "extends InputComponent",
24
+ "new": null,
25
+ "note": "This release's single class-member-collision entry: it covers EVERY exported class whose member surface changed, so a consumer who EXTENDS a DS component can resolve them in one pass. Subclassing a DS component is unsupported (design-system.md § Components), but where it happens the names collide: TS4114 demands `override`, TS2415 fires on a redeclared private member, TS2416 on a differing signature. (1) The 14 message-bearing FIELD classes (Input, Textarea, Select, DatePicker, TimePicker, Autocomplete, Checkbox, Switch, RadioGroup, Radio, OtpInput, Slider, ColorPicker, MultiSelect) REMOVED the protected `messageState` computed, and DatePickerComponent also removed `messageText`; all 14 ADDED the `error`, `warning`, `errors` and `touched` inputs plus protected `message` and `invalidResolved`, with DatePickerComponent also gaining private `localError` and `dateInvalid`. (2) Both CVA base classes (`DsControlValueAccessor`, `DsBooleanControlValueAccessor`) gained a protected `touchedSelf`. (3) `AppLayoutComponent` gained public `railOverlay` and `railId`. (4) `TableComponent` REMOVED the `clientSort` input and gained `sortModeResolved`, `sortableCol()`, `exporting`, `runExport()`, `virtualizing`, `virtualRowHeight`, `virtualWindow`, `windowData` and `isStriped()`, plus the `persistLayout`, `storageKey`, `exportButton`, `exportFilename`, `exportFetcher`, `virtualScroll` and `virtualRowSize` inputs. (5) `ButtonComponent` gained `ariaControls`; `IconButtonComponent` gained `ariaExpanded` and `ariaControls`. (6) `CheckboxComponent`, `SwitchComponent` and `RadioComponent` REMOVED the protected `devMode`. (7) `LayoutScrollService` gained `scroller`, `scrollTo()`, `configureRestore()`, `consumePendingOffset()` and `contentReady()`. (8) The `close()` method on SelectComponent, AutocompleteComponent, MultiSelectComponent, DatePickerComponent, TimePickerComponent, ColorPickerComponent and PopoverComponent gained an optional `cause` parameter, as did TimePickerComponent's `onEscape()` — an override declared as `close()` still satisfies the base, so this one only bites a subclass that re-declares the parameter list differently. ACTION: rename the subclass's own member, or add `override` where the base's semantics genuinely match; a subclass that overrode `messageState` should move its logic to an `error` / `warning` binding on the element instead, since the message is now resolved centrally. Consumers who only use the <ds-...> elements in templates need no change.",
26
+ "searchHints": [
27
+ "extends InputComponent",
28
+ "extends SelectComponent",
29
+ "extends TextareaComponent",
30
+ "extends DatePickerComponent",
31
+ "extends CheckboxComponent",
32
+ "extends AppLayoutComponent",
33
+ "extends TableComponent",
34
+ "extends ButtonComponent",
35
+ "extends IconButtonComponent",
36
+ "extends DsControlValueAccessor",
37
+ "extends ",
38
+ "messageState",
39
+ "override readonly"
40
+ ]
41
+ },
42
+ {
43
+ "id": "select-label-class-renamed-to-label",
44
+ "kind": "class-rename",
45
+ "old": "ds-select .select-label",
46
+ "new": ".label",
47
+ "note": "STYLING ONLY, and only for a consumer who styles ds-select's internal DOM. The label element is now `.label`, the same class every other field in the family uses, so a rule written as `.select-label` (or the doubled `.select-label.select-label` needed to out-rank the shimmed component rule) silently matches nothing after the upgrade. Retarget to `.label`, scoped to the element: `ds-select .label { … }`. In most cases the rule can be DELETED instead — it existed to make the select's label match the input's, and they now match by default. Scope strictly to selectors under ds-select; `.label` is also the class ds-input, ds-textarea, ds-date-picker, ds-time-picker and ds-radio-group use.",
48
+ "searchHints": [
49
+ "select-label",
50
+ ".select-label",
51
+ "ds-select",
52
+ "label",
53
+ "field-label"
54
+ ]
55
+ },
56
+ {
57
+ "id": "radio-group-label-class-and-type",
58
+ "kind": "class-rename",
59
+ "old": "ds-radio-group .group-label",
60
+ "new": ".label",
61
+ "note": "TWO changes to the same element. (1) CLASS: `ds-radio-group`'s label is now `.label`, so consumer CSS targeting `.group-label` under ds-radio-group stops matching — retarget or delete. Note `.group-label` is ALSO the class `ds-sidenav-group` uses for its heading, which is unchanged; only rules scoped under ds-radio-group are affected. (2) VISIBLE: the label now draws the family's type - `--font-weight-bold` at `--font-size-xs` - instead of its own `--font-weight-medium` at `--font-size-s` on `--line-height-flat`. It was the only field label drawing its own, and in a form beside an input or select it read as a different kind of element. ACTION: none for most screens, since matching the family is the point. To keep the old look, scope the family tokens: `ds-radio-group { --ds-field-label-weight: var(--font-weight-medium); --ds-field-label-font-size: var(--font-size-s); }`.",
62
+ "searchHints": [
63
+ "group-label",
64
+ ".group-label",
65
+ "ds-radio-group",
66
+ "radio-group",
67
+ "label"
68
+ ]
69
+ },
70
+ {
71
+ "id": "ng-add-schematic-now-loads",
72
+ "kind": "behavior",
73
+ "old": "ng add @ids-group-ltd/ids-design-system",
74
+ "new": null,
75
+ "note": "`ng add` never actually ran its schematic in any released version, so the DS global styles were NEVER wired automatically - every consumer either did it by hand or shipped without them. The package is `\"type\": \"module\"` while the compiled schematic was CommonJS, so Node refused to load it: \"exports is not defined in ES module scope\". The build wrote a nested schematics/package.json with {\"type\":\"commonjs\"} to fix exactly that, and `npm pack` silently DROPPED it - npm treats a directory holding a package.json as a separate package root - so the marker existed in dist/ and was absent from the tarball. The schematic is now `.cts` compiled to `.cjs`, which survives packing. ACTION: consumers who added `@use '@ids-group-ltd/ids-design-system/styles/ds';` to their global stylesheet by hand need do nothing - ng add prepends the same line and skips when it is already present. Consumers who never wired the styles (and whose components therefore render unthemed) can now run `ng add` and have it work, or add that one line themselves.",
76
+ "searchHints": [
77
+ "ng add",
78
+ "ng-add",
79
+ "styles/ds",
80
+ "@use '@ids-group-ltd",
81
+ "schematics"
82
+ ]
83
+ },
84
+ {
85
+ "id": "menu-item-radius-default-now-square",
86
+ "kind": "behavior",
87
+ "old": "ds-menu",
88
+ "new": null,
89
+ "note": "DEFAULT CHANGED, visual: a `ds-menu` row's hover/active fill was `var(--radius-md)` (8px) and is now SQUARE — the new `--ds-menu-item-radius` token defaults to `0`. In the same change `ds-menu` dropped its own `padding: var(--space-1)` to `padding: 0` and gained `overflow: hidden`, so rows now run edge to edge and the panel's own corner clips the first and last row. The reason: a curve at zero inset can never be concentric with the panel's, and inside a `ds-popover` (which drops its padding for a menu) the row's 8px sat against the popover's 12px corner and left visible slivers at the top and bottom of the list. ACTION: none for consumers happy with the new look. To restore the old rounded highlight set `ds-menu { --ds-menu-item-radius: var(--radius-md); }`; to also restore the old 4px inset around the rows add your own `ds-menu { padding: var(--space-1); }`, because the panel padding has NO token. Setting a radius without restoring some padding is the one combination to avoid — the corners have nothing to curve away from.",
90
+ "searchHints": [
91
+ "ds-menu",
92
+ "ds-menu-item",
93
+ "--ds-menu-item-radius",
94
+ "menu-item",
95
+ "ds-popover"
96
+ ]
97
+ },
98
+ {
99
+ "id": "menu-divider-spacing-default-now-zero",
100
+ "kind": "behavior",
101
+ "old": "ds-menu-divider",
102
+ "new": null,
103
+ "note": "DEFAULT CHANGED, visual: `ds-menu-divider` carried `padding: var(--space-1) 0` (4px above and below) on top of the `gap: var(--space-0-5)` (2px) that `ds-menu` already puts between rows, so a separated group read as a hole — 6px + line + 6px where adjacent items sat 2px apart. The divider's padding now defaults to `0` through the new `--ds-menu-divider-spacing` token, so the line takes one row's place instead of adding a second gap. Menu items keep their own 8px/12px padding, so the line still separates without help. ACTION: none unless you want the old airier boundary back, in which case set `ds-menu { --ds-menu-divider-spacing: var(--space-1); }`. Affects only menus that actually use `ds-menu-divider`.",
104
+ "searchHints": [
105
+ "ds-menu-divider",
106
+ "--ds-menu-divider-spacing",
107
+ "menu-divider",
108
+ "ds-menu"
109
+ ]
110
+ },
111
+ {
112
+ "id": "time-picker-panel-radius-now-panel-role",
113
+ "kind": "behavior",
114
+ "old": "ds-time-picker",
115
+ "new": null,
116
+ "note": "DEFAULT CHANGED, visual: the `ds-time-picker` dropdown panel's corner radius was `var(--radius-md)` (8px) and is now `var(--ds-radius-panel)` (`--radius-lg`, 12px). It was the one floating panel in the library still drawing the CONTROL radius — its own sibling `ds-date-picker` has always drawn the panel role, so the two pickers rendered different corners side by side in the same form. The radius was also the only property on that element with no public hook (fill, border and shadow all had one). ACTION: none unless you want the old 8px corner back, in which case set `ds-time-picker { --ds-time-picker-panel-radius: var(--radius-md); }` — the new hook is forwarded onto the portaled overlay pane, so a per-instance override on the element does reach the panel. Affects only the open dropdown; the trigger's radius is unchanged and still resolves through `--ds-time-picker-trigger-radius`.",
117
+ "searchHints": [
118
+ "ds-time-picker",
119
+ "--ds-time-picker-panel-radius",
120
+ "--ds-time-picker-trigger-radius",
121
+ "time-panel",
122
+ "time-picker"
123
+ ]
124
+ },
125
+ {
126
+ "id": "focus-partial-needs-use-line",
127
+ "kind": "code-add",
128
+ "old": "@use '@ids-group-ltd/ids-design-system/styles",
129
+ "new": "@use '@ids-group-ltd/ids-design-system/styles/focus';",
130
+ "note": "ONLY for a consumer who cherry-picks DS style partials individually instead of importing the bundled `styles/ds` entry. The `data-focus` focus-style switch AND the `@media (forced-colors: active)` fallback both live in the new `styles/_focus.scss` partial. A consumer of the bundled entry gets both automatically and must do NOTHING — the partial is `@forward`ed from `styles/ds`. A consumer who @uses partials à la carte gets NEITHER until they add this line to the same global stylesheet: without it, the `data-focus` attribute silently does nothing, and — the part that matters for accessibility — focused elements have NO visible indicator at all in Windows High Contrast / forced-colors mode, because forced-colors drops box-shadow and the shadow-only indicator was all they had. Site: the global stylesheet that already @uses the other DS partials. Do NOT add it alongside a `styles/ds` import; that entry already includes it.",
131
+ "searchHints": [
132
+ "@use '@ids-group-ltd/ids-design-system/styles",
133
+ "styles/ds",
134
+ "styles/focus",
135
+ "ids-design-system/styles",
136
+ "data-focus",
137
+ "forced-colors"
138
+ ]
139
+ },
140
+ {
141
+ "id": "combobox-tokens-renamed-to-picker",
142
+ "kind": "removed-api",
143
+ "old": "--combobox-offset / --combobox-maxh",
144
+ "new": "--picker-offset / --picker-maxh",
145
+ "note": "The two global tokens sizing the listbox panel shared by ds-autocomplete and ds-multi-select kept the name of a component that no longer exists - ds-combobox was renamed to ds-autocomplete on 2026-07-07. ACTION, only if you overrode them: rename --combobox-offset to --picker-offset and --combobox-maxh to --picker-maxh. These are global scale tokens, not --ds-* component tokens, so nothing else changes and the values are unchanged.",
146
+ "searchHints": [
147
+ "--combobox-offset",
148
+ "--combobox-maxh",
149
+ "combobox"
150
+ ]
151
+ }
152
+ ],
153
+ "informational": [
154
+ "Every field gained `error` and `warning` beside `hint`, resolved on a fixed ladder: `error` (an explicit string, shown at once) → validation errors → `warning` → `hint`. Only ONE line renders, so a field's height does not depend on how many sources are populated. Purely additive: a field that binds only `hint` behaves exactly as before, and when something is invalid but no source produced text the `hint` still renders in the error state — so the pre-existing `[invalid]` + `[hint]=\"errorText\"` idiom keeps working untouched.",
155
+ "Fields now read validation state from the bound form control, so `error` is optional. Signal forms binds `errors` and `touched` automatically (those input names are Angular 21's `FormUiControl` contract) and already drove the value through the `ControlValueAccessor` DS fields have always implemented. Reactive and template-driven forms need NO new binding: the field resolves `NgControl` after first render and subscribes to `control.events`. Errors wait for the first blur, or for the parent form to be submitted, so a `required` error never greets an untouched form. `invalid` is now OR-ed with what the control reports; the explicit input still wins.",
156
+ "`DS_CONFIG` gained `field.errorMessages` — one shared map from validation-error kind to text, for errors whose validator carried no message (Angular's built-ins never do). A message on the error itself always wins, so `required(path, { message })` in signal forms or `{ myError: 'text' }` from a plain validator overrides the map per case. An error that resolves to no text anywhere warns in dev instead of rendering an error style with an empty line.",
157
+ "`dsRailTrigger` is a new directive: put it on your own burger anywhere inside `ds-app-layout` and it toggles `[(railOpen)]` and keeps `aria-expanded` / `aria-controls` pointing at the rail panel, so the trigger and the panel are related for a screen reader. Both attributes are dropped while the rail is not an overlay, where `aria-expanded=\"false\"` would contradict what the user sees. `ds-app-layout` also exposes `railId` and the read-only `railOverlay` signal for a consumer that builds its own trigger.",
158
+ "`ds-table` `sortMode=\"none\"` is the way to render a column that is sortable in principle but not on this screen: the header renders as plain text, with no button, caret or `aria-sort`, instead of a control that does nothing.",
159
+ "Bugfix, no action: a CLOSED compact `ds-app-layout` rail is now `inert`, and closing it (Escape, scrim click, navigation) returns focus to the control that claims the rail via `aria-controls`. Before, the off-canvas panel kept `role=\"dialog\"`/`aria-modal=\"true\"`, left every nav link tabbable and stranded the caret inside the hidden panel, because cdkTrapFocusAutoCapture restores focus only on directive destroy. A consumer whose custom burger sets neither `dsRailTrigger` nor `aria-controls` gets the inert fix but no focus return - add `aria-controls` pointing at `ds-app-layout`'s `railId` to get it.",
160
+ "Bugfix, no action: NESTING one `ds-app-layout` inside another now works. Three separate faults are fixed. (1) The rail's open state was written as `:host(.rail-open) &`, which Angular's emulated encapsulation compiles to a DESCENDANT selector, and every instance of a component shares one encapsulation attribute — so an inner layout's rail opened whenever an outer one was open, and the inner scrim swallowed clicks meant for the outer. The state now lives on the elements it styles (`.rail.open` / `.scrim.open`). (2) Below `lg` the rail was `position: fixed`, resolving against the viewport, so an embedded layout threw its rail over the top-left of the WINDOW; rail and scrim are now `absolute` against a `position: relative` host. (3) The host now also sets `isolation: isolate`, so each layout z-indexes its rail (`--layer-drawer`) and scrim in its own stacking context instead of the one root context, where an inner layout's rail could paint over an outer layout's open rail. All three are identical to the old behaviour for a single full-viewport shell, which is the normal case.",
161
+ "Bugfix, no action: `--ds-overlay-enter-scale` is now forwarded onto the portaled overlay pane, so scoping it per instance (`ds-select { --ds-overlay-enter-scale: 0.9; }`) finally reaches select / multi-select / autocomplete / date / time / colour picker / popover / tooltip / menu-submenu panels. 0.7.1 shipped it as a known gap — the token was resolved on the pane but absent from the forwarded set, while the other four enter tokens did forward. A GLOBAL override worked before and is unaffected.",
162
+ "The field family gained one label contract: --ds-field-label-font-size / -weight / -color / -transform / -tracking, resolved by ds-input, ds-textarea, ds-select, ds-date-picker, ds-time-picker and ds-radio-group through a shared mixin. Defaults equal the values those components hard-coded, so nothing moves unless you set a token. There is deliberately no per-component token set - custom-property scoping already narrows a retune to one element (`ds-select { --ds-field-label-transform: uppercase; }`) - and -transform/-tracking make the uppercase tracked label reachable through tokens for the first time. ds-input's --ds-input-label-color/-fs/-fw still take precedence where set and now fall through to the family token rather than the raw scale.",
163
+ "`--ds-field-height` is new, and the --field-h-sm/-md/-lg scale is now actually read by ds-input, ds-select, ds-date-picker and ds-time-picker - previously only -lg was, the other two sizes reaching past the scale to the raw --hit-min/--hit-cozy. Values are identical, so no height moves on upgrade. NO ACTION, but two things become possible that silently did nothing before: retuning --field-h-md (or -sm) now moves every field, and --ds-field-height pins one height regardless of the size class, scopable per component. NOT a fix for unequal picker heights - those were already equal as of 0.7.1's aligned trigger geometry.",
164
+ "ds-button gained --ds-button-font-size / -weight / -tracking / -height / -pad-x / -pad-y, and reflects data-variant / data-color on its host element for external targeting. Defaults equal the hard-coded values, so nothing moves. NO ACTION - but a consumer who wrote .button.button.button { font-size; font-weight; letter-spacing; padding; height } to out-rank the shimmed .button.md can replace it with the tokens, set on the host. Per-variant --ds-button-* values were ALREADY reachable from the host before this change (the colour/fill resolvers read the hook first and never declare it), so an indirection layer added to work around that can go too.",
165
+ "ds-app-layout gained opt-in restoreScroll + restoreScrollTimeout, and LayoutScrollService gained contentReady() and consumePendingOffset(). Off by default, so NO ACTION. Turn it on for a list-and-details app and going back returns the reader to their place; forward links still land at the top. A 'back to list' control that adds a history entry instead of traversing must pass state: { dsRestoreScroll: true } to be restored. Note that an app which scrolls on navigation itself (an anchor jump, a URL that names a section) writes after the layout and wins, so restoreScroll is a no-op on those routes.",
166
+ "New role layer between the foundation scales and components: --ds-radius-{inner,control,panel,pill}, --ds-elevation-{raised,overlay,floating,modal}, and --ds-motion-{enter-panel,enter-surface,enter-large,exit,exit-large}-{duration,easing}. Every role defaults to the value its members already used, so NO ACTION and nothing moves visually. What becomes possible: retune one family without hitting the others - re-round panels while buttons keep their radius, lift every overlay in one line, make panel entrances snappier once. The old --shadow-popover/-modal/-toast/-card aliases still work and now resolve THROUGH the elevation roles. A per-component --ds-<comp>-radius / -shadow / -enter-duration override still wins over its role. Note: two motion resolvers (ds-loading-overlay, the toast leave) deliberately stay on the raw scale because they use --ease-standard, which no role carries.",
167
+ "New global focus-style switch: set data-focus=\"ring\" | \"field\" | \"edge\" | \"outline\" on <html>. Omitting it keeps the current split (halo on fields, double ring on controls), so NO ACTION for a consumer of the bundled `styles/ds` entry — it picks up both the switch and the forced-colors fallback automatically. (A consumer who cherry-picks partials à la carte DOES have one line to add; that is the actionable `focus-partial-needs-use-line` item.) Also new, and not part of the switch: under @media (forced-colors: active) every focused element gets a CanvasText outline, because forced-colors drops box-shadow and a shadow-only focus indicator disappeared there entirely.",
168
+ "ds-table gained [persistLayout] + storageKey (round-tripping columnOrder, columnWidths and hiddenKeys through localStorage) and [exportButton] + exportFilename + exportFetcher. All opt-in and off by default, so NO ACTION. A consumer who wrote their own localStorage effect for the three column models, or their own export button, can delete both - together with the sortValue accessor these were the last three reasons to keep a wrapper around ds-table. exportCsv() is unchanged for existing callers and now accepts an optional row set as its second argument.",
169
+ "New component ds-password-rules: the live requirement checklist under a new-password field. Purely additive, NO ACTION. A consumer with a hand-rolled password checklist can replace it - pass the rule set as { label, test } pairs (the policy stays yours, it has to mirror your server), bind [value] to the field and [showUnmet] to whether the user has tried to submit. Exposes metCount and allMet for gating a submit button, and the standalone passwordRulesMet(value, rules) function — the same predicate that backs allMet — for gating one without rendering the list. Also exported: the DsPasswordRule ({ label, test }) and DsPasswordRuleState ('pending' | 'met' | 'failed') types for typing the rule set, plus a listId input that names the <ul> so a field's aria-describedby can point at the checklist.",
170
+ "ds-input gained ariaDescribedBy, merged with the field's own message id rather than replacing it - for describing a field with a password-rule list or a policy note. Additive, NO ACTION. Note that setting aria-describedby on the <ds-input> element itself does NOT work: it lands on the wrapper, not the inner input.",
171
+ "New component ds-auth-shell: the scaffold for the screens in front of the login (sign-in, forgot password, reset, MFA), counterpart to ds-app-layout. Purely additive, NO ACTION. A consumer with a hand-rolled auth scaffold can replace it: brand lockup + optional tagline + one card holding the form + a support line. The brand row is the ds-sidenav row - same brand / logoLetter / [dsBrandName] contract and the same letter-mark tile - so it is NOT the string-splitting brandAccent the ports used; project [dsBrandName] to tint a slice of the wordmark. Card body is the default slot, the support line goes in [dsAuthSupport] (a real <footer>, so it carries the contentinfo landmark). cardElevation / cardPadding pass through to ds-card. Tokens: --ds-auth-shell-min-height, -card-max-width, -gap, -bg-color, -mark-bg-color, -mark-label-color. WORTH KNOWING when porting: the shell owns the full-height box itself, so do NOT wrap it in your own 100vh/100dvh container - the ports that stacked two scrolled a page whose content fits. It also adds env(safe-area-inset-*) padding, and centres with auto margins rather than centre alignment so a form taller than the box stays reachable when the shell is embedded at min-height 100%.",
172
+ "New component ds-filter-bar: a Priority+ filter row - as many filters as fit inline, the rest behind a \"+N more\" panel. Purely additive, NO ACTION. A consumer with a hand-rolled filter row (or one that wraps to two lines on a laptop) can replace it. Each filter goes in an <ng-template [dsFilterItem]=\"180\"> carrying the width it should occupy; the bar decides the split from those numbers plus a ResizeObserver on the row. Trailing controls (search, Clear) carry the dsFilterBarTrailing attribute - mark each control, do NOT wrap them in a div: the bar owns that group's gap and alignment, and a projected wrapper is a plain block whose children stack. Tokens: --ds-filter-bar-gap, --ds-filter-bar-panel-gap. Inputs moreLabel and panelLabel exist for translation. WORTH KNOWING: the declared width is a contract, not a hint - the slot is sized to exactly that number, so declare what the control actually occupies. And because a filter that collapses is MOVED into the panel, its view is destroyed and re-created: internal state such as an open dropdown or focus does not survive that, while its value does (it lives in your signal or form control). Content that reaches the bar with neither slot marker is dropped, with a dev-mode console warning.",
173
+ "ds-table gained virtual scrolling: [virtualScroll]=\"true\" plus virtualRowSize (px). Opt-in and off by default, so NO ACTION. Only the rows in view stay in the DOM (~25 regardless of row count), padded by two spacer rows so the scrollbar still spans the whole data set. REQUIRES maxHeight - a bounded scroller is the viewport it windows against, and without one nothing is virtualized (dev warning). CONSTRAINTS in virtual mode, all enforced rather than assumed: every row is exactly virtualRowSize tall (the CSS height comes from that same input), table-layout becomes fixed, and cells are kept to one line - so declare column widths, and do not rely on wrapping cell text there. Row EXPANSION is suppressed with a dev warning (an expanded row is taller than virtualRowSize and every offset below it would be wrong); pageSize alongside virtualScroll is also warned about, since virtual scrolling is what pagination was for. Sorting, filtering, selection, sticky header, sticky first column and column resizing all keep working. NOT built on the CDK virtual-scroll viewport on purpose: that wraps the table in a transformed content wrapper, and the transform breaks this table's sticky header and sticky first column. STILL OPEN: lazy loading (fetching slices from a server as they scroll into view) is NOT part of this - see the backlog item.",
174
+ "FIXED in ds-table: with stickyHeader and stickyFirstColumn both on, the first body row painted OVER the header in the pinned columns, so the header read as that row's data. --table-sticky-corner-z was already there to keep the corner above the body, but the sticky-header rule out-specified it and both ended up at the same z-index, where DOM order puts the body on top. No action needed - it is a pure CSS fix. If you worked around it with your own z-index on DS table cells, that override can go.",
175
+ "ds-checkbox / ds-switch / ds-radio now RENDER a projected caption instead of dropping it, and expose the caption's colour and size. Additive, NO ACTION - [label] stays the documented API and still wins when both are supplied. If you added a dev-warning workaround after 0.7.1 (moving markup-bearing captions into a string), you can move them back: <ds-checkbox>I accept the <a href=...>Terms</a></ds-checkbox> now works. ONE DIFFERENCE: the required asterisk comes with [label] only - a projected caption owns its own marker, since only your markup knows where it belongs. New hooks: --ds-checkbox-label-color / -label-font-size, the same pair on ds-switch, and --ds-radio-label-font-size (--ds-radio-label-color already shipped). The font-size hook beats the size class. These are deliberately NOT part of the --ds-field-label-* contract: a label above an input is a heading for the field and reads secondary, a caption beside a checkbox is the content being agreed to and reads primary. If you were overriding the caption colour with a descendant selector against .control-text, replace it with the token.",
176
+ "Overlay panels now fade out when DISMISSED and still close instantly when something is CHOSEN. No action - behaviour only. Escape, a press outside, or the page scrolling away fades the panel over --ds-motion-exit-duration (120ms); picking an option, pressing the trigger again, or Tab still closes instantly, because a fade on a deliberate choice reads as the panel lagging behind it. Applies to select, autocomplete, multi-select, date-picker, time-picker, color-picker and popover. Tune with --ds-overlay-leave-duration / --ds-overlay-leave-easing, or set the duration to 0ms to get the old always-instant close everywhere. Reduced motion already zeroes it. A fading panel is pointer-events: none, so it cannot swallow a click aimed at what is behind it. If you built anything that assumed the overlay pane is removed from the DOM synchronously on Escape, note that it now lives for one exit duration longer (the component state - open(), overlayRef - is still cleared immediately).",
177
+ "design-system.md now states the --ds-* token contract once instead of repeating it per component, and carries a warning that its hand-written API and token lists have drifted from the code (ds-button is documented with its pre-color/variant API and the pre-rename --ds-button-bg / -fg names). For the authoritative surface use the auto-generated Component API tables and token reference in ds-docs, which are extracted from source on every build. No action - documentation only."
178
+ ]
179
+ }
@@ -0,0 +1,157 @@
1
+ {
2
+ "version": "0.9.0",
3
+ "items": [
4
+ {
5
+ "id": "leave-keyframes-renamed",
6
+ "kind": "token-rename",
7
+ "old": "modal-out / ds-sheet-down / ds-sheet-fade-out / drawer-panel-close-right|left|top|bottom / drawer-scrim-out",
8
+ "new": "ds-fade-out / ds-scale-out / ds-slide-out / ds-slide-edge-out",
9
+ "note": "REMOVED: seven exit @keyframes local to modal, drawer and bottom-sheet are gone, replaced by four GLOBAL presets mirroring the entrance vocabulary. ACTION: nothing, unless you referenced one of the old names - only possible from a global stylesheet, since they were view-encapsulated. If you did, the mapping is: modal-out, ds-sheet-fade-out and drawer-scrim-out -> ds-fade-out; ds-sheet-down and all four drawer-panel-close-* -> ds-slide-edge-out. WHY: teardown matched the animation NAME on animationend, so the exit could not be swapped without breaking close entirely; the guard now checks the event came from the animated element rather than a child, which frees the name. WHAT YOU GAIN: --ds-modal-leave-keyframes, --ds-drawer-leave-keyframes and --ds-bottom-sheet-leave-keyframes, the exit counterparts of the --ds-*-enter-keyframes you already have. Point one at your own GLOBAL @keyframes - a component-scoped name is renamed by Angular and will not resolve. An exit preset reads --_ds-exit-x/y/scale and falls back to the matching --_ds-enter-*, so a surface that leaves the way it arrived declares nothing. VERIFY AFTER UPGRADING: open and close a modal, a drawer and a bottom sheet and confirm the page scrolls again afterwards - a teardown that does not fire leaks the body-scroll lock, which is the failure this change could cause and the one we tested for.",
10
+ "searchHints": [
11
+ "modal-out",
12
+ "ds-sheet-down",
13
+ "drawer-panel-close",
14
+ "drawer-scrim-out",
15
+ "ds-sheet-fade-out"
16
+ ]
17
+ },
18
+ {
19
+ "id": "dropdown-panel-radius",
20
+ "kind": "behavior",
21
+ "old": "--radius-md (8px) on the ds-select / ds-multi-select panel",
22
+ "new": "--ds-radius-panel (12px)",
23
+ "note": "CHANGED DEFAULT, visual: the dropdown panel behind ds-select and ds-multi-select has a 12px corner, was 8px. It was the one panel outside the radius role layer - modal, popover, date-picker, time-picker, autocomplete, bottom-sheet, card, stat and page-footer all resolve --ds-radius-panel already - so it both disagreed with its siblings and could not be retuned through the role a consumer is told to use. ACTION: none unless you want the old corner, in which case set --ds-select-panel-radius: 8px, or --ds-radius-panel: 8px to move every panel together. CHECK: a screen where a dropdown opens beside a popover or a date picker - that is where the 4px difference was visible and is now gone.",
24
+ "searchHints": [
25
+ "--radius-md",
26
+ "dropdown-panel",
27
+ "ds-select",
28
+ "--ds-radius-panel"
29
+ ]
30
+ },
31
+ {
32
+ "id": "auth-shell-selector-to-auth-layout",
33
+ "kind": "selector-rename",
34
+ "old": "ds-auth-shell",
35
+ "new": "ds-auth-layout",
36
+ "note": "Component renamed (shipped as ds-auth-shell in the tagged 0.8.0 source, its only release under that name). \"Shell\" is not this library's word for a layout: the app-level one was renamed ds-app-shell -> ds-app-layout in 0.7.0, and calling the auth counterpart a shell put the split vocabulary back. ACTION: rename the element and its closing tag. Behaviour, inputs and slots are unchanged - brand, logoLetter, tagline, cardElevation, cardPadding, [brand], [dsBrandName] and dsAuthSupport all keep their names. Also rename the class and the tokens (separate entries below).",
37
+ "searchHints": [
38
+ "ds-auth-shell"
39
+ ]
40
+ },
41
+ {
42
+ "id": "auth-shell-class-to-auth-layout",
43
+ "kind": "type-rename",
44
+ "old": "AuthShellComponent",
45
+ "new": "AuthLayoutComponent",
46
+ "note": "The exported component class renamed alongside the ds-auth-shell -> ds-auth-layout selector. Update imports and any type references. No members changed.",
47
+ "searchHints": [
48
+ "AuthShellComponent"
49
+ ]
50
+ },
51
+ {
52
+ "id": "auth-shell-tokens-to-auth-layout",
53
+ "kind": "token-rename",
54
+ "old": "--ds-auth-shell-",
55
+ "new": "--ds-auth-layout-",
56
+ "note": "Prefix rename for the six component tokens: --ds-auth-shell-min-height / -card-max-width / -gap / -bg-color / -mark-bg-color / -mark-label-color -> --ds-auth-layout-*. Values and defaults are unchanged. DS-owned tokens only (no others ship under this prefix); a consumer's own --ds-auth-shell-* variable is out of scope. EXCLUDED, do not rename: the global scale token --auth-card-w, the fallback behind -card-max-width, which carries no --ds-auth-shell- prefix and keeps its name. Confirm the new name exists in the installed package.",
57
+ "searchHints": [
58
+ "--ds-auth-shell-"
59
+ ]
60
+ },
61
+ {
62
+ "id": "search-height-joins-field-scale",
63
+ "kind": "behavior",
64
+ "old": "ds-search",
65
+ "new": null,
66
+ "note": "CHANGED DEFAULT: ds-search is 40px tall at the default size, was 36px. Every size moved onto the field scale - sm var(--field-h-sm) 32px (was --hit-min 32px, unchanged), md var(--field-h-md) 40px (was --search-h 36px, CHANGED), lg var(--field-h-lg) 48px (unchanged). The old 36px was a lone tier: nothing else in the library used it, while ds-button, ds-input, ds-select and both pickers all resolve --field-h-md, so a search box in a toolbar sat 4px short of every neighbour. RESTORE the old height with `ds-search { --ds-search-height: 36px; }` - that token still wins over everything. ALSO NEW: the height now falls through --ds-field-height, so `--ds-field-height: 44px` on a toolbar levels search along with the fields, which was the point of the change.",
67
+ "searchHints": [
68
+ "ds-search",
69
+ "--ds-search-height",
70
+ "--search-h"
71
+ ]
72
+ },
73
+ {
74
+ "id": "search-h-token-removed",
75
+ "kind": "removed-api",
76
+ "old": "--search-h",
77
+ "new": null,
78
+ "note": "The global --search-h token is gone; it existed only to hold ds-search's 36px and nothing reads it any more. Its replacements, in precedence order: --ds-search-height (retunes search alone) and --ds-field-height (levels the whole field family). If you declared --search-h to resize search, that declaration is now inert - swap it for --ds-search-height with the same value. Reading it in your own CSS resolves to nothing. The --hit-md scale token it pointed at (36px) is untouched and still available.",
79
+ "searchHints": [
80
+ "--search-h"
81
+ ]
82
+ },
83
+ {
84
+ "id": "table-sort-filter-mode-default-server",
85
+ "kind": "behavior",
86
+ "old": "ds-table",
87
+ "new": null,
88
+ "note": "CHANGED DEFAULT: ds-table sortMode and filterMode resolve to 'server' when unset, were 'client'. An undeclared table now emits (sortChange) / updates columnFilters and reorders or filters NOTHING itself. ACTION, and it is per-table: if the table receives ALL its rows - the giveaway is that it does NOT bind `total` - add sortMode=\"client\" and, where any column has filter: 'set', filterMode=\"client\", or its headers will look live and do nothing. If it binds `total` it is server-paged and the new default is what you already wanted: the old 'client' sorted only the page in hand, so the rows looked sorted and were not, and a dev warning said exactly that. Tables that already declare a mode are untouched. A reversed dev warning now fires on the client case (no `total` + sortable/filterable columns + no declared mode), so run the app and let the console list them.",
89
+ "searchHints": [
90
+ "ds-table",
91
+ "sortMode",
92
+ "filterMode",
93
+ "sortable",
94
+ "sortChange"
95
+ ]
96
+ },
97
+ {
98
+ "id": "number-stepper-lg-height",
99
+ "kind": "behavior",
100
+ "old": "ds-number-stepper",
101
+ "new": null,
102
+ "note": "CHANGED DEFAULT, one size only: ds-number-stepper with size=\"lg\" is 48px tall, was 44px. It resolved --hit-comfy while the field family's large size is --field-h-lg (--hit-touch, 48px), so a large stepper was a step short of a large input beside it. The +/- buttons and the quantity box derive their widths from that height, so they widen with it. size=\"sm\" (32px) and the size=\"md\" default (40px) are unchanged. RESTORE with `ds-number-stepper { --ds-field-height: 44px; }` scoped to the instance, or set the size back to md.",
103
+ "searchHints": [
104
+ "ds-number-stepper",
105
+ "size=\"lg\"",
106
+ "--hit-comfy"
107
+ ]
108
+ },
109
+ {
110
+ "id": "tabs-url-param-adoption",
111
+ "kind": "code-add",
112
+ "old": "ds-tabs",
113
+ "new": "urlParam=\"tab\"",
114
+ "note": "ds-tabs can now keep the active tab in the URL: set urlParam (e.g. urlParam=\"tab\") and the strip writes ?tab=<name>, so the tab survives F5, a shared link and the Back button. Nothing changes until you set it, but this is worth a deliberate pass rather than a skim. ACTION, per strip: (1) GIVE EACH ds-tab A `value` if it has none - the URL is written from value, falling back to label, so without one a link carries the visible label and breaks the moment the label is translated or reworded. (2) ONE STRIP PER PARAMETER NAME. Two ds-tabs sharing a name on the same screen erase each other: both write the same query parameter, and a reload restores whichever wrote last. A dev-mode warning now names the clash. Nested or sibling strips need distinct names (tab, subtab). (3) DELETE any hand-rolled wiring - a queryParamMap subscription plus a navigate() on tabChanged is exactly what this replaces, and running both fights. Behaviour to expect: NAMES not indices (an index would silently repoint every old link as soon as a tab is inserted), the FIRST tab writes no parameter, every write uses replaceUrl so flipping tabs does not fill the Back button, and an unknown or missing name lands on the first tab instead of throwing. Inert outside a routed context, and being query-only it does not trip ds-app-layout's scroll reset.",
115
+ "searchHints": [
116
+ "<ds-tabs",
117
+ "ds-tabs",
118
+ "tabChanged",
119
+ "queryParamMap"
120
+ ]
121
+ }
122
+ ],
123
+ "informational": [
124
+ "--ds-radius-inner now actually reaches the small affordances. 33 reads across fifteen component stylesheets took var(--radius-sm) directly - dropdown options, field clear buttons, calendar days, chips, tag and toast close buttons - so the role a consumer is told to retune reached exactly one component. They resolve the role now, and its default IS --radius-sm, so NOTHING MOVES: verified by measuring a component page before and after, identical surfaces at identical radii. NO ACTION, but it changes what a square brand costs you: zeroing the three roles used to leave five surfaces rounded and now leaves one. Two deliberate exclusions - five focus-ring radii inside :focus-visible keep following the raw scale (a ring traces a box, it is not a brand surface), and the shared dropdown panel behind ds-select / ds-multi-select still reads --radius-md (8px) where every other panel resolves --ds-radius-panel (12px). That last one is a tracked inconsistency, not a hook: squaring it needs the scale. Worked example on the Theming page.",
125
+ "A 32px toolbar is `density=\"compact\"`, not a per-control height pin. Measured on a nine-control row: search, input, select, autocomplete, date-picker, time-picker, multi-select, number-stepper and button are all 40px by default and all 32px under [data-density=\"compact\"] on the container. DELETE-LIST MATERIAL: if you pin --ds-search-height (or any sibling) to get a shorter row - one consumer pins --hit-min and its comment complains that md used to be 36px - that pin can go, and after the height contract it was fighting the family rather than joining it. Known limit at the bottom of the scale: ds-multi-select and ds-autocomplete hold chips, so they set a min-height rather than a height and stop following the floor once it drops below what the text needs - under ultra-compact they are 33px and 29px where the rest reach 24px, because a density tier scales padding and hit targets but not the type scale. Compact is unaffected in practice (33 against 32). Documented on the Density page.",
126
+ "SIGNAL FORMS WORK — no adapter, no wrapper, no DS import. Put [formField] from @angular/forms/signals on any DS control and the form owns the value, validation, touched and disabled state. This was ALWAYS nearly true and nobody knew: FormValueControl requires exactly one member, a `value` model(), and every DS control already had it. Measured across all fifteen controls - thirteen bound with no library change at all. Additive, NO ACTION. WHAT CHANGED HERE, and it is why the other four rules now work too: min/max/maxLength on ds-input, ds-textarea and ds-number-stepper accept undefined on the WRITE side (the binder sends it for an unset bound; the read type is untouched); `readonly` joins ds-input, ds-textarea and ds-select as the contract spelling of the existing readOnly, because signal forms binds by NAME and a readonly() rule was reaching nothing; `minLength` and `pattern` are new native attributes on ds-input and ds-textarea; and `hidden` is declared on both control-value-accessor bases, so a hidden() rule now removes the control on all thirteen that carry one. focus() is implemented too, so focusBoundControl() - the usual way to reach the first invalid field after a failed submit - lands on the element that holds the value rather than on the host, which is a <ds-*> element and not focusable, so focus previously went nowhere. It resolves per control: the stepper's number box rather than its minus button, the tabbable radio rather than the first in the DOM, a picker's trigger rather than an input inside its closed panel. NOT implemented: dirty, pending and disabledReasons - the form still tracks them, and they are blocked on a visual decision rather than wiring. ERROR TEXT still comes from your validator: required(path.email, { message: '...' }) or a provideDsConfig field.errorMessages mapping, otherwise the field goes red with no words and only a dev warning explains why. Docs: the Practice > Signal Forms page, with a live form and the measured contract table.",
127
+ "ds-modal / ds-modal-card gained [dividers] (default true = today's rendering). Additive, NO ACTION - but DELETE-LIST MATERIAL if you set --ds-modal-divider: transparent. Two consumer apps did exactly that, and both were then left with header and actions padding sized to clear a rule that was no longer drawn, stacking into a 35px gap where 16px was wanted; one needed !important plus a stylelint-disable to win it back. [dividers]=\"false\" drops the rules AND the padding in one move, because those are one design decision. If you kept a deliberate --ds-modal-divider colour, nothing changes. If you set it transparent, replace it with [dividers]=\"false\" and delete whatever padding overrides you wrote afterwards - and note --ds-modal-body-pad-y now falls to 0 in that mode, so set it explicitly if you want a value in both.",
128
+ "ds-modal / ds-modal-card gained a [title-badge] content slot and a subtitle input, so a dialog header can carry a status chip and a second line without abandoning the component. Additive, NO ACTION - both are absent by default and the header renders exactly as before. WORTH A LOOK IF YOU HAND-ROLLED A DIALOG: a consumer audit found two screens that dropped ds-modal purely because the header could not hold `title + ds-badge` over a `carrier - type` line, and re-implemented the scrim, the body scroll lock, backdrop-click and Escape by hand - losing the focus trap, focus restore, the enter/leave animation and, in one case, the footer, which put a destructive action next to the close button. The shape matches ds-page-header: [title-badge] projects beside the title, subtitle is a plain string under it. The accessible name is still the title string - projected markup never enters aria-labelledby. Retune with --ds-modal-subtitle-text-color and --ds-modal-subtitle-font-size.",
129
+ "HUMAN GUIDE: migrations/unreleased/README.md walks this release in order — where to look for each change, the one call that needs judgement per table (sortMode/filterMode), and a section this project had never written before: WHAT YOU CAN NOW DELETE. Two dogfooding audits found that most consumer workarounds were written against hooks that already existed, because nothing ever told them a thing had been tokenised. Read section 3 even if the upgrade itself is clean.",
130
+ "NEW COMPONENT ds-field-group: several controls in one bordered box (select + input, input + button, search + date-picker). Additive, NO ACTION. If you hand-rolled a glued row by stripping borders off two controls and wrapping them, this replaces it - wrap them in <ds-field-group> and mark the stretching one with grow. Six controls can be segments: ds-input, ds-select, ds-search, ds-autocomplete, ds-date-picker, ds-button. ds-number-stepper and ds-multi-select are excluded by design. Grouped controls must not be given a label or hint - the message row would break the glued line and is suppressed.",
131
+ "ds-table gained [lazy] + (lazyLoad) for fetching rows as they scroll into view. Additive and opt-in, NO ACTION. If you paged a long list yourself to keep it responsive, this is the alternative: set lazy with virtualScroll and total, make data a SPARSE array total long, and write each fetched row at its ABSOLUTE index - gaps inside the window render skeleton rows. Note sortMode must not be \"client\" (it would sort only the rows that happen to have arrived); the new server default is already right.",
132
+ "--ds-field-height now reaches ds-autocomplete, ds-multi-select, ds-color-picker, ds-number-stepper, ds-split-button and the ds-modal confirm input. All six spelled their height as the raw --hit-* value, so the token the name advertises did nothing for them; they read the field scale now. Pixel-identical at every size EXCEPT ds-number-stepper at size=\"lg\" (its own actionable entry above). NO ACTION unless you had already worked around the gap by pinning height on one of these - that pin can go.",
133
+ "The six connected panels (ds-select, ds-multi-select, ds-autocomplete, ds-color-picker, ds-date-picker, ds-time-picker) now build their overlay from one shared helper instead of six identical copies. Internal only, NO ACTION: the position, the 4px gap, the flip-above fallback, the panel classes and the scroll strategy are byte-for-byte what they were.",
134
+ "ds-autocomplete gained dsAutocompletePrefix / dsAutocompleteSuffix content slots and [showChevron] (default true). Additive, NO ACTION. If you absolutely positioned a search glyph over the field and re-padded the input, or hid the arrow with a global rule reaching for .autocomplete-chevron, replace both: put the icon in the prefix slot and set [showChevron]=\"false\". The slot names and behaviour match ds-input's dsInputPrefix / dsInputSuffix.",
135
+ "ds-autocomplete gained a public clear() that empties the value AND the typed text. If you reset the field by querying the inner <input> out of the DS's DOM and dispatching a synthetic input event, delete that and call clear() on a viewChild ref - the DOM shape it depended on is not part of the public API. It deliberately does not move focus.",
136
+ "ds-autocomplete gained --ds-autocomplete-panel-radius (default --ds-radius-panel) and --ds-autocomplete-panel-maxh (default --picker-maxh). NO ACTION - both defaults equal today's values. The radius one matters if you square the radius roles: the autocomplete panel was the last portaled surface hard-coding --radius-lg, so it stayed rounded in an otherwise square brand. The max-height one replaces reaching for the private --picker-maxh, which ds-multi-select also reads.",
137
+ "ds-table gained --ds-table-head-pad-top / --ds-table-head-pad-bottom, plus showPageSize and showLabel forwarded to its footer pager. All additive with today's values as defaults, NO ACTION. Separately FIXED: density=\"compact\" pinned padding onto the cells, which out-specified every --ds-table-*-pad-* hook, so a compact table silently ignored all of them; it now retunes the density tokens instead. Spacing is unchanged - but if you fought that with an !important, it can go.",
138
+ "ds-date-picker and ds-time-picker resolve their trigger's horizontal padding from --field-pad-x (new hooks: --ds-date-picker-trigger-pad-x, --ds-time-picker-trigger-pad-x) instead of a hard-coded --space-3. Identical at the default density; the difference shows under [data-density], where the token shrinks and the literal did not, leaving a picker 8px wider than the input beside it. NO ACTION unless you hand-pinned picker padding to compensate.",
139
+ "The ds-auth-shell -> ds-auth-layout rename is vocabulary only: no input, output, slot, token value or behaviour changed, and it is the same component 0.8.0 shipped. If you never adopted ds-auth-shell (it was added in 0.8.0), there is nothing to do.",
140
+ "FIXED in ds-textarea: size=\"sm\" and size=\"lg\" rendered the md vertical padding (12px top and bottom) regardless of the size. The size blocks set the inner textarea's vertical pad, but a :host-prefixed pin at the end of the file out-ranked them once emulated encapsulation shimmed both selectors - it carries one more attribute than the size selector. There are now three pins, one per size, and the size blocks keep only the horizontal padding they own. NO ACTION: the change is visible only on a non-md textarea and the md default is unchanged. Note that retuning --ds-input-pad-y previously moved all three sizes together; if you compensated for the wrong padding with your own override on a sm or lg textarea, that override now stacks on the corrected value and can go.",
141
+ "ds-auth-layout now COMPRESSES its own chrome on a short viewport: block padding, the column gap, the letter-mark tile and the masthead inner gap clamp against svh. No action - behaviour only, and a viewport 800px tall or more renders exactly what it did before. Read that as a VIEWPORT height, not a screen size: a 1366x768 laptop sits near 630px after browser and OS chrome, and a 1080p screen at 150% display scaling near 585px, so plenty of desktops do get the compressed furniture - an earlier wording of this line said 'so desktop is unchanged', which was wrong. Type is deliberately NOT clamped: the wordmark and the tile's glyph were measured to buy zero vertical space (the tile sets the row height at every viewport, and the glyph sits in a fixed-size box) while flattening the brand against a fixed 14px tagline, so both keep the fixed sizes 0.8.0 ships. Below 800px the remaining furniture shrinks so it is not what pushes a card into scrolling (~131px instead of ~219px at a landscape phone's ~330px). Two tokens opt out per dimension: --ds-auth-layout-pad-block and --ds-auth-layout-mark-size; setting any of those or the existing --ds-auth-layout-gap to a fixed value stops that one compressing. A card taller than the remaining space still scrolls - that is intended.",
142
+ "ds-auth-layout audit fixes, all additive or corrective - NO ACTION. The letter-mark tile is now aria-hidden (a screen reader announced 'A MyAdmin', now 'MyAdmin') and carries flex-shrink: 0 so a long wordmark cannot squash it out of square; logoLetter on its own renders its tile instead of nothing; the glyph is taken by code point rather than charAt(0), which returned half a surrogate pair for a brand starting with an emoji; box-sizing: border-box is declared on the host rather than inherited, so the component still avoids its own overflow scrollbar for a consumer composing style partials without styles/reset. The four env(safe-area-inset-*) calls gained 0px fallbacks and moved to physical padding-left/padding-right so the insets cannot swap sides under RTL - and note they are inert unless YOUR app sets viewport-fit=cover in its viewport meta, which the library cannot set for you. New tokens, both defaulting to today's behaviour: --ds-auth-layout-mark-radius (the tile's radius was the one value with no override hop) and --ds-auth-layout-brand-max-height (none by default; set it to cap a projected [brand] logo, which nothing constrained). New input landmark, default 'none': set landmark=\"main\" on a standalone auth page so the card - an <article>, which is not a landmark - becomes something a screen-reader user can jump to; it stays opt-in because this layout is also embedded inside pages that already own a main.",
143
+ "ds-icon now logs a dev-mode warning when an icon name is in neither the DS set nor your provideDsIcons() registry - previously it rendered an empty <svg> silently. No action, and nothing changes in production. Expect the warning to surface real typos the moment you upgrade: an audit of three screens in one consumer is what prompted it.",
144
+ "ds-app-layout gained scrollReset: \"path\" | \"never\" | \"always\" (default \"path\" = existing behaviour, so NO ACTION), and LayoutNavigationService is now exported. If you wrote your own \"did the path change?\" check to work around the layout resetting scroll - or to skip a view transition, or to reset a tab - replace it with inject(LayoutNavigationService).pathChanged: it is NavigationEnd, path only, de-duplicated, and it skips a navigation carrying state: { dsSamePage: true }. Note a naive split(\"?\") is NOT equivalent, it keeps the fragment this stream strips. To stop the layout resetting scroll on a paged or filtered list, set scrollReset=\"never\" and call LayoutScrollService.scrollToTop() where you actually want it.",
145
+ "Options in ds-select / ds-autocomplete / ds-multi-select panels now have a pressed state (they had hover only, which does nothing on touch). No action - visual only. If you styled :active on .option yourself to work around it, you can drop that override; if you want a different pressed fill, it reads --surface-muted (neutral rows) and --primary-subtitle (the selected row).",
146
+ "ds-table gained filterMode: \"client\" | \"server\" | \"none\" (default \"client\" = existing behaviour, so NO ACTION) and columnFilterOptions. If your table is server-paged (you bind `total`) and any column has filter: \"set\", you WANT filterMode=\"server\" plus columnFilterOptions with the real value domain - otherwise the checklist offers only the values on the current page and then filters locally on top of the server. A dev warning now points this out.",
147
+ "ds-table gained dsHeaderFilter, a template slot for a header filter the built-in checklist cannot express (date range, numeric threshold, async options). Additive, NO ACTION. If you built a host-owned popover outside the table for this, you can move it inside: <ng-template dsHeaderFilter=\"key\" [active]=\"...\" let-close=\"close\">. The table keeps the button, the popover and the active styling; `active` is how you tell it your criterion is set, and `close` dismisses the panel after applying. A projected filter also makes the column filterable on its own - you do not additionally need filter: \"set\".",
148
+ "ds-table now announces sort state and row range through its role=\"status\" region (\"Sorted by Owner, ascending\", \"Showing 1-25 of 240\"). No action - it is additive and the first render stays silent, since aria-live announces changes rather than initial content. If you added your own live region around the table for this, remove it or you will get double announcements. Wording is overridable per table through the sortAnnouncement and rangeAnnouncement inputs, which take the facts and return the sentence.",
149
+ "ds-table column resizing is now keyboard-operable: the handle is focusable (role=\"separator\", labelled per column) and answers Arrow (16px), PageUp/PageDown (64px) and Home (back to automatic sizing). No action. If you hid or restyled .col-resize, note it can now receive focus and shows an indicator.",
150
+ "ds-table exportFetcher may now resolve a Blob or a URL string as well as rows, so a backend-formatted file downloads as-is; a new exportFailed output emits the rejection. Additive, NO ACTION - returning rows keeps working. If you wrapped the button to catch failures yourself, you can drop that.",
151
+ "ds-table: the FIRST column resize now freezes every visible column at its measured width before applying the drag, so untouched columns stop jumping. No action, but if you persist columnWidths (persistLayout) expect the stored map to gain entries for columns the user never dragged - that is the fix, not a bug.",
152
+ "ds-table sortValue string comparison now uses sensitivity: \"base\" alongside numeric: true, so mixed-case and accented values sort together. No action; if you relied on case-sensitive ordering, pass your own sortValue returning a normalized key.",
153
+ "ds-date-picker keeps its trigger indicator while the panel is open (an \"open\" class alongside the focus rules). Visual only, NO ACTION. If you styled .trigger:focus-within yourself to work around the trigger going dark, you can drop it.",
154
+ "ds-autocomplete in single mode collapses its filter input once a value is chosen and the panel is closed, so the field reads as a picker instead of a text box. Visual only, NO ACTION. Clicking the field still opens the panel and expands the input, and typing still filters. If you set --ds-autocomplete-input-minw to work around the empty box, you can drop it.",
155
+ "ds-date-picker: clicking the calendar glyph no longer moves focus into the day grid. It now behaves like a click on the field - with allowInput (the default) the caret stays in the field, and a read-only field still focuses the grid. No action; ArrowDown on the field enters the grid as before. If you scripted tests that assumed a glyph click lands focus on a day button, they need updating."
156
+ ]
157
+ }
@@ -30,9 +30,16 @@ See `AUTHORING.md` for how to write a good entry.
30
30
  **Prose guides per version.** The `<version>.json` manifest is the terse machine mirror. When a
31
31
  release needs a longer human walkthrough (a worked before/after, a mental model, edge cases the
32
32
  `note` can't hold), put it in a sibling folder named for that version: `migrations/<version>/*.md`
33
- (e.g. `migrations/0.5.1/badge-statuses.md`). The folder never matches the `*.json` glob, so tooling
33
+ (e.g. `migrations/0.5.1/badge-statuses.md`, `migrations/unreleased/README.md`). The folder never matches the `*.json` glob, so tooling
34
34
  ignores it; the manifest `note` and the CHANGELOG point at the guide by path.
35
35
 
36
+ **A guide should carry the half a manifest cannot: what the consumer can now DELETE.** Two
37
+ dogfooding audits (mm-ecm 08-06, mm-broker 08-07) read consumer stylesheets as a record of what
38
+ this library made them write, and both found the same thing — most workarounds were written
39
+ against hooks that ALREADY existed, because a release note says what broke and never says what
40
+ became unnecessary. `unreleased/README.md` §3 is the first guide to carry that list; treat it as
41
+ the shape to follow.
42
+
36
43
  **Authoring:** drafted at release time alongside the CHANGELOG entry (the `/changelog` workflow
37
44
  drafts it from the release diff; the release author reviews). The prose changelog stays canonical
38
45
  for humans — the manifest is its machine mirror; if they disagree, fix the manifest.
@@ -0,0 +1,134 @@
1
+ # Migrating to the next release
2
+
3
+ The manifest (`../unreleased.json`) is the terse machine mirror — what a tool applies.
4
+ This is the human half: **where to look, what to change, and what you can now delete.**
5
+
6
+ > **If you are on 0.7.x**, you are taking two releases at once. Read the 0.8.0 notes
7
+ > first; everything below is on top of them.
8
+
9
+ ---
10
+
11
+ ## 1. What breaks — eight things, by where you will find them
12
+
13
+ Work through them in this order. The first three are one rename and are best done together.
14
+
15
+ ### In your templates
16
+
17
+ | Look for | Change to | Notes |
18
+ | --- | --- | --- |
19
+ | `<ds-auth-shell>` | `<ds-auth-layout>` | Inputs, outputs and slots all keep their names |
20
+ | `sortMode` / `filterMode` **absent** on a `ds-table` | Add `sortMode="client"` (and `filterMode="client"`) **if the table holds every row** | The default flipped to `"server"`. See §2 |
21
+
22
+ ### In your TypeScript
23
+
24
+ | Look for | Change to |
25
+ | --- | --- |
26
+ | `AuthShellComponent` | `AuthLayoutComponent` |
27
+
28
+ ### In your stylesheets
29
+
30
+ | Look for | Change to | Notes |
31
+ | --- | --- | --- |
32
+ | `--ds-auth-shell-*` | `--ds-auth-layout-*` | Six tokens. **Do not** rename `--auth-card-w` — it carries no such prefix |
33
+ | `--search-h` | `--ds-search-height`, or `--ds-field-height` for the whole family | The global token is gone; a declaration of it is now inert |
34
+
35
+ ### Visual changes to eyeball
36
+
37
+ - **`ds-search` is 40px tall, was 36px.** It was the only control in the library on that
38
+ height. Restore with `ds-search { --ds-search-height: 36px; }` if your toolbar depends
39
+ on it — but see §3 first, because a pin may not be what you want.
40
+ - **`ds-number-stepper` at `size="lg"` is 48px, was 44px.** Other sizes unchanged.
41
+
42
+ ### Worth a deliberate pass, not a find/replace
43
+
44
+ - **Signal Forms bind to DS controls.** `<ds-input [formField]="f.email" />` — that is the whole
45
+ integration; `[formField]` comes from `@angular/forms/signals`, not from this library. Thirteen
46
+ of fifteen controls already bound before this release; the other two, and the `readonly()`,
47
+ `pattern()`, `minLength()` and `hidden()` rules, work now. If you hand-bound
48
+ `[value]="f.x().value()" (valueChange)="f.x().value.set($event)"` per field, **all of that can
49
+ go.** Give each validator a `message`, or map the kinds once in `provideDsConfig`, or the field
50
+ turns red with no words. See the Practice → Signal Forms page.
51
+
52
+ - **`ds-tabs` can now own the URL.** Set `urlParam="tab"` and the active tab survives F5,
53
+ a shared link and the Back button. Per strip: give each `ds-tab` a `value` (the URL is
54
+ written from it, so without one your links carry the visible label and break when it is
55
+ reworded), use **one parameter name per strip** (two strips sharing a name erase each
56
+ other — there is a dev warning), and delete any hand-rolled `queryParamMap` + `navigate()`
57
+ wiring, which would otherwise fight it.
58
+
59
+ ---
60
+
61
+ ## 2. The one that needs judgement per table
62
+
63
+ `sortMode` and `filterMode` default to `'server'` now, where they used to default to
64
+ `'client'`.
65
+
66
+ **Why it changed:** server-paged is the normal case, and there the old default was
67
+ actively wrong — the table sorted the page in hand, so rows looked sorted and were not.
68
+
69
+ **How to decide, per table:**
70
+
71
+ - **Binds `total`?** It is server-paged. The new default is what you wanted; do nothing.
72
+ - **Does not bind `total`?** It almost certainly holds every row. Add `sortMode="client"`,
73
+ and `filterMode="client"` if any column has `filter: 'set'` — otherwise the headers stay
74
+ clickable and do nothing.
75
+
76
+ **How to find them all:** run the app in dev and read the console. A reversed dev warning
77
+ now fires on exactly the case that needs your attention (no `total`, sortable or filterable
78
+ columns, no declared mode) and names each table.
79
+
80
+ ---
81
+
82
+ ## 3. What you can now DELETE — the half a migration guide usually leaves out
83
+
84
+ Two dogfooding audits (mm-ecm 2026-08-06, mm-broker 2026-08-07) read consumer stylesheets
85
+ as a record of what this library made them write. Both found the same thing: **most of the
86
+ workarounds were written against hooks that already existed** — the consumer had no signal
87
+ that anything had been tokenised since. That is a failure of these notes, not of the
88
+ consumer, so here is the list.
89
+
90
+ Search your styles for these; if you find them, they can go.
91
+
92
+ | If you have | Delete it, because |
93
+ | --- | --- |
94
+ | `.button.button.button { … }` or rules against `.v-outline` / `.c-secondary` | `ds-button` reflects `[data-variant]` and `[data-color]` on the HOST. Use `ds-button[data-variant="outline"]` |
95
+ | `--radius-sm: 0` to square a checkbox | `--ds-checkbox-radius` |
96
+ | `.title.title { font-size }` inside a modal | `--ds-modal-title-font-size` |
97
+ | Pagination label type overrides | `--ds-pagination-label-*` |
98
+ | `.size { display: none }` on a pager | `[showPageSize]="false"` — and it is now forwarded through `ds-table` too |
99
+ | `.actions:empty { display: none }` on a modal | The library already ships it |
100
+ | `--ds-modal-divider: transparent`, plus whatever you rewrote the modal padding to afterwards | `[dividers]="false"` — it drops the rules *and* the padding that existed to clear them |
101
+ | A defensive hover rule on the selected dropdown row | The `:not(.is-selected)` branch already handles it |
102
+ | `ds-menu-divider { padding: 0 }` | `--ds-menu-divider-spacing`, which already defaults to 0 |
103
+ | A dozen scattered `--ds-*-radius: 0` | For a fully square brand, four lines: `--radius-sm/md/lg/xl: 0` (leave `--radius-pill`). Measured — the three ROLES alone leave options, clear buttons and dropdown panels rounded; they are the tool for squaring one family and keeping another. Worked example on the Theming page |
104
+ | A global rule squaring `.ds-overlay-pane` | Radius and elevation roles now travel onto portaled panes when the host overrides them |
105
+ | Absolutely positioning a search glyph over an autocomplete, or hiding `.autocomplete-chevron` | `dsAutocompletePrefix` and `[showChevron]="false"` |
106
+ | Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it | `clear()` |
107
+ | A hand-built KPI tile whose value is a badge | `ds-stat` takes a projected `[dsStatValue]` |
108
+ | A pinned `--ds-search-height` (or any sibling) to get a shorter control row | `density="compact"` on the container — every field control is 32px there, measured |
109
+ | A hand-rolled `.scrim` + `.panel` dialog, written because the modal header could not hold a badge or a second line | `ds-modal` projects `[title-badge]` and takes a `subtitle`. You get back the focus trap, focus restore, the scroll lock, Escape and the footer |
110
+ | `[value]="f.x().value()" (valueChange)="f.x().value.set($event)"` on every field of a signal form | `[formField]="f.x"` — the control implements the contract already |
111
+ | `white-space: normal` forced onto a badge in a table cell | `--ds-badge-white-space` |
112
+ | `::ng-deep .card { height: 100% }` for equal-height cards | The card's box fills a stretched host on its own |
113
+ | `!important` on `ds-table` cell padding under `density="compact"` | Compact no longer out-specifies the padding hooks |
114
+ | A wrapper around `ds-table` for sort/range announcements, keyboard column resize, or a header filter the checklist cannot express | All three ship: the live region, the `role="separator"` handle, and `dsHeaderFilter` |
115
+
116
+ **How to check you got them all:** grep your styles for `::ng-deep`, `!important` and any
117
+ selector naming a DS internal class (`.button`, `.trigger`, `.option`, `.modal`). Each hit
118
+ is either a genuine gap worth reporting or an entry in the table above.
119
+
120
+ ---
121
+
122
+ ## 4. After you bump
123
+
124
+ - **Run the app in dev with the console open.** The library warns about the combinations it
125
+ cannot fix for you: undeclared sort/filter mode, duplicate `urlParam`, lazy without
126
+ `virtualScroll`, an unknown icon name, a projected stat value with an orphaned `unit`.
127
+ Every warning names the component and what to do.
128
+ - **Check a toolbar and a form row side by side.** The field-height contract moved
129
+ `ds-search`, so anything you had lined up by hand is worth a second look. If you pin
130
+ heights per component, consider `[data-density]` instead — it retunes the whole family at
131
+ once and survives the next change of this kind.
132
+ - **Tell us what you had to hand-roll.** The delete list in §3 exists because two consumers
133
+ wrote forty lines of workarounds against hooks that were already there. If you are
134
+ reaching into a DS internal, that is a gap worth filing.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ids-group-ltd/ids-design-system",
3
- "version": "0.7.1",
3
+ "version": "0.9.0",
4
4
  "description": "IDS Group Angular design system: components, tokens, themes",
5
5
  "license": "MIT",
6
6
  "homepage": "https://ids-ds.proto.ids-group.co.uk/",
@@ -3,7 +3,7 @@
3
3
  "schematics": {
4
4
  "ng-add": {
5
5
  "description": "Wire the IDS design system's global styles into a project.",
6
- "factory": "./ng-add/index#ngAdd",
6
+ "factory": "./ng-add/index.cjs#ngAdd",
7
7
  "schema": "./ng-add/schema.json"
8
8
  }
9
9
  }