@ids-group-ltd/ids-design-system 0.10.1 → 0.10.3

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,482 @@
1
+ {
2
+ "version": "0.10.2",
3
+ "items": [
4
+ {
5
+ "id": "resolved-readbacks-are-public",
6
+ "kind": "behavior",
7
+ "old": "class MyThing extends ButtonComponent (or any DS component)",
8
+ "new": null,
9
+ "note": "Every readback that resolves through DS_CONFIG changed from `protected` to public: `sizeResolved` on fourteen controls, `elevationResolved` and `paddingResolved` (ds-card), `withDotResolved` (ds-badge), `borderedResolved` and `stickyScrollbarResolved` (ds-table), `dividersResolved` (ds-modal and ds-modal-card), `reserveMessageResolved` (every field, via DsFieldBase), the date/time picker locale and format resolvers, and `brandName` / `letterGlyph` / `taglineText` (ds-sidenav, ds-auth-layout). WHY: 0.10.0 told consumers to read `sizeResolved()` now that `size()` returns null when unbound, and that did not compile -- reading it from a host, a test or a viewChild was TS2445. NO ACTION for a consumer that composes. ACTION only if you SUBCLASS a DS component and declare a member with one of those names: it is now a public member of the base, so an incompatible re-declaration needs `override` or a rename. Members a host can derive from its own bindings stay protected on purpose: `invalidResolved`, `railResolved`, `sortModeResolved`, `filterModeResolved`.",
10
+ "searchHints": [
11
+ "sizeResolved",
12
+ "elevationResolved",
13
+ "paddingResolved",
14
+ "withDotResolved",
15
+ "borderedResolved",
16
+ "dividersResolved",
17
+ "reserveMessageResolved",
18
+ "brandName",
19
+ "letterGlyph",
20
+ "extends ButtonComponent"
21
+ ],
22
+ "surface": "typescript",
23
+ "verify": "No consumer subclass redeclares a `*Resolved` readback as protected, and a host that reads `sizeResolved()` off a DS component compiles.",
24
+ "supersedes": [
25
+ "0.10.0#control-size-input-becomes-nullable"
26
+ ]
27
+ },
28
+ {
29
+ "id": "focus-ring-inner-transparent",
30
+ "kind": "behavior",
31
+ "old": "--focus-ring-inner: var(--surface-canvas)",
32
+ "new": null,
33
+ "note": "The 2px gap between an element and its focus ring no longer paints a named surface; it is transparent, so it shows whatever is actually behind. NO ACTION on a canvas-coloured ground -- the same pixels show through. It CHANGES what you see where the focused element sits on something else: a white card in a dark app used to get a dark rim around it, which read as a rendering artifact. If you deliberately relied on an opaque gap -- e.g. to hold the ring off a busy photo background -- set `--focus-ring-inner` back to a colour on that scope. Also new and unrelated to this remap: `data-focus=\"inset\"` draws the same ring INSIDE the border box, for a subtree under an `overflow: hidden` ancestor that would otherwise clip the ring away entirely. Unlike the other focus styles it is not pinned to :root -- set it on the clipping element.",
34
+ "searchHints": [
35
+ "--focus-ring-inner",
36
+ "focus-ring",
37
+ "data-focus",
38
+ "surface-canvas",
39
+ "overflow: hidden",
40
+ "--ds-control-focus-shadow"
41
+ ],
42
+ "surface": "style",
43
+ "restore": "--focus-ring-inner: var(--surface-canvas);",
44
+ "verify": "No stylesheet still assumes an opaque ring gap: `--focus-ring-inner` is either unset, or set deliberately on the non-canvas ground that needs it."
45
+ },
46
+ {
47
+ "id": "max-visible-chips-null-is-unset-multi-select",
48
+ "kind": "value-remap",
49
+ "old": "ds-multi-select[maxVisibleChips]",
50
+ "new": null,
51
+ "note": "BREAKING VALUE REMAP. `null` used to be the LOUDEST setting - render every chip and let the trigger wrap - and it now means 'unset', resolving to 'fit' (measure the trigger, show what fits) like every other nullable input since 0.10.0. Bind the new 'all' mode to keep the old behaviour. This covers the ATTRIBUTE and the BINDING form alike: [maxVisibleChips]=\"null\", [maxVisibleChips]=\"undefined\", and any expression, field or method that can EVALUATE to null feeding that binding - retype those to `number | 'fit' | 'all' | null` and return 'all' where they meant show-them-all. A numeric value is unchanged (still a ceiling, still measured), 'fit' is unchanged, and leaving the input unbound is unchanged because 'fit' was already the default. SUPERSEDES the 0.10.0 guidance: that release told you to bind [maxVisibleChips]=\"null\" to keep every chip. If you did, that binding now means \"unset\" and resolves to \"fit\" — change it to \"all\".",
52
+ "searchHints": [
53
+ "maxVisibleChips",
54
+ "[maxVisibleChips]",
55
+ "maxVisibleChips="
56
+ ],
57
+ "map": {
58
+ "null": "maxVisibleChips=\"all\"",
59
+ "fit": "maxVisibleChips=\"fit\""
60
+ },
61
+ "surface": [
62
+ "template",
63
+ "typescript"
64
+ ],
65
+ "detect": [
66
+ "[maxVisibleChips]=\"null\"",
67
+ "maxVisibleChips",
68
+ "'fit'"
69
+ ],
70
+ "supersedes": [
71
+ "0.10.0#chips-cap-by-width-by-default"
72
+ ]
73
+ },
74
+ {
75
+ "id": "max-visible-chips-null-is-unset-autocomplete",
76
+ "kind": "value-remap",
77
+ "old": "ds-autocomplete[maxVisibleChips]",
78
+ "new": null,
79
+ "note": "BREAKING VALUE REMAP. `null` used to be the LOUDEST setting - render every chip and let the trigger wrap - and it now means 'unset', resolving to 'fit' (measure the trigger, show what fits) like every other nullable input since 0.10.0. Bind the new 'all' mode to keep the old behaviour. This covers the ATTRIBUTE and the BINDING form alike: [maxVisibleChips]=\"null\", [maxVisibleChips]=\"undefined\", and any expression, field or method that can EVALUATE to null feeding that binding - retype those to `number | 'fit' | 'all' | null` and return 'all' where they meant show-them-all. A numeric value is unchanged (still a ceiling, still measured), 'fit' is unchanged, and leaving the input unbound is unchanged because 'fit' was already the default. SUPERSEDES the 0.10.0 guidance: that release told you to bind [maxVisibleChips]=\"null\" to keep every chip. If you did, that binding now means \"unset\" and resolves to \"fit\" — change it to \"all\".",
80
+ "searchHints": [
81
+ "maxVisibleChips",
82
+ "[maxVisibleChips]",
83
+ "maxVisibleChips="
84
+ ],
85
+ "map": {
86
+ "null": "maxVisibleChips=\"all\"",
87
+ "fit": "maxVisibleChips=\"fit\""
88
+ },
89
+ "surface": [
90
+ "template",
91
+ "typescript"
92
+ ],
93
+ "detect": [
94
+ "[maxVisibleChips]=\"null\"",
95
+ "maxVisibleChips",
96
+ "'fit'"
97
+ ],
98
+ "supersedes": [
99
+ "0.10.0#chips-cap-by-width-by-default"
100
+ ]
101
+ },
102
+ {
103
+ "id": "max-visible-chips-type-widened",
104
+ "kind": "behavior",
105
+ "old": "maxVisibleChips: number | 'fit' | null",
106
+ "new": null,
107
+ "note": "TYPE WIDENING on ds-autocomplete and ds-multi-select, breaking for READERS and OVERRIDERS, not for writers - the same asymmetry 0.10.0's two widenings had, where the consumer's type-checker was the only finder. A binding compiles as before; what stops compiling is an explicitly typed declaration that has to accept the value (`const cap: number | 'fit' | null = ...`, a helper parameter, a viewChild target) and a subclass override, because the `equal` type-parameter position of InputSignalWithTransform is invariant (TS2416). ACTION: retype to `number | 'fit' | 'all' | null`, or drop the annotation and let inference carry it. The VALUE change that comes with it is the separate max-visible-chips-null-is-unset-* pair; this entry is only the declaration.",
108
+ "searchHints": [
109
+ "maxVisibleChips",
110
+ "InputSignalWithTransform",
111
+ "extends MultiSelectComponent",
112
+ "extends AutocompleteComponent"
113
+ ],
114
+ "surface": "typescript",
115
+ "detect": [
116
+ "number | 'fit' | null",
117
+ "number | 'fit'",
118
+ "maxVisibleChips"
119
+ ],
120
+ "verify": "Every explicit annotation that has to hold a maxVisibleChips value accepts 'all', and no subclass override declares the old union."
121
+ },
122
+ {
123
+ "id": "sidenav-active-item-is-a-wash",
124
+ "kind": "behavior",
125
+ "old": "--ds-sidenav-item-bg-color-active",
126
+ "new": null,
127
+ "note": "VISUAL CHANGE with no required edit, plus one override that should now GO. The active ds-sidenav-item filled with --accent and labelled itself --text-on-primary; it is now a wash (--accent-subtitle) behind an --accent-strong label, and the active-hover mix goes toward the accent (--accent-muted) instead of 88% toward white, which was invisible on a wash. Material fills its drawer's active item with secondary-container and Carbon with $background-selected; neither uses the brand accent. NO TOKEN WAS RENAMED - every --ds-sidenav-item-*-active hook keeps its name, so an app that already retuned them looks exactly as it did and needs no change. ACTION only if you replaced the solid pill yourself (two apps did): compare your override against the new default and drop it if they now agree, since keeping it means maintaining a copy of the DS default. SEPARATELY: the edge rail is an input now - [rail]=\"false\" on ds-sidenav drops it for every item and [rail] on ds-sidenav-item overrides that per item (unset = follow the parent). If you hid the rail with `--ds-sidenav-item-rail: transparent` or a ::ng-deep box-shadow reset, both still work, but the input is the supported route. SidenavContract gained a required `rail: () => boolean` member - only relevant if you provide the SIDENAV token yourself, which nothing outside the library is expected to do. THE RAIL ALSO CHANGED COLOUR, and this one is a contrast fix rather than a taste call: it was --secondary (#FF7B2E) and is now --accent-strong, the active label's own colour. An orange bar across a monochrome-blue row measured 2.33:1 on the light wash, under the 3:1 floor a non-text indicator needs; the accent measures 6.16:1 light and 5.28:1 dark. RESTORE the old bar with `--ds-sidenav-item-rail: var(--secondary)` if the second hue was deliberate.",
128
+ "searchHints": [
129
+ "--ds-sidenav-item-bg-color-active",
130
+ "--ds-sidenav-item-label-color-active",
131
+ "--ds-sidenav-item-rail",
132
+ "ds-sidenav-item",
133
+ "SidenavContract"
134
+ ],
135
+ "surface": "style",
136
+ "restore": "ds-sidenav-item { --ds-sidenav-item-bg-color-active: var(--accent); --ds-sidenav-item-label-color-active: var(--text-on-primary); }",
137
+ "verify": "The app either has no --ds-sidenav-item-*-active override, or the override it keeps is one it still wants beside the new wash default."
138
+ },
139
+ {
140
+ "id": "exported-class-members-grew",
141
+ "kind": "behavior",
142
+ "old": "extends TableComponent",
143
+ "new": null,
144
+ "note": "This release's class-member-collision entry, the counterpart of 0.8.0's, 0.9.0's and 0.10.0's: subclassing a DS component is unsupported (design-system.md), but where it happens a new base member with the same name stops the build - TS4114 demands `override`, TS2415 fires on a redeclared private. GAINED MEMBERS, per `npm run class-surface` against v0.10.1: AutocompleteComponent and MultiSelectComponent (chipsMode, showsEveryChip); MenuItemComponent (description, descriptionId); SearchComponent (disabled, isDisabled); SidenavComponent (rail); SidenavItemComponent (rail, railResolved); TableComponent (actionReason, actionsFor, hasActionsFor, visibleRowActions). NO members were lost. CHANGED SIGNATURES, which collide differently: SearchComponent.clear() went protected to public and SearchComponent.focus() now carries `override` (it overrides the CVA base) - a subclass that redeclared either needs `override` and a compatible signature. ACTION: rename the subclass's own member, or add `override` where the base's semantics genuinely match. The separate resolved-readbacks-are-public entry covers the protected-to-public sweep across fourteen classes, which collides the same way. Consumers who only use the <ds-...> elements in templates need no change. LATER THE SAME DAY, from a second `npm run class-surface` run after the overlay-guard fix: TimeColumnsComponent is unchanged but TimePickerComponent also gained the private `insideATrigger` - a redeclared private fails with TS2415 exactly like a public collision, which is why a private counts here at all. AND, from the state-glyph work: `messageIcon` on all FIFTEEN field components (AutocompleteComponent, CheckboxComponent, ColorPickerComponent, DatePickerComponent, InputComponent, MultiSelectComponent, OtpInputComponent, RadioComponent, RadioGroupComponent, SegmentedComponent, SelectComponent, SliderComponent, SwitchComponent, TextareaComponent, TimePickerComponent), plus `iconResolved` and `config` on FieldMessageComponent - which is internal and not exported, so it only matters to a fork.",
145
+ "searchHints": [
146
+ "extends TableComponent",
147
+ "extends SearchComponent",
148
+ "extends SidenavItemComponent",
149
+ "extends MultiSelectComponent",
150
+ "extends AutocompleteComponent",
151
+ "extends MenuItemComponent",
152
+ "override ",
153
+ "TS4114",
154
+ "extends TimePickerComponent",
155
+ "messageIcon",
156
+ "extends InputComponent"
157
+ ],
158
+ "surface": "typescript",
159
+ "detect": [
160
+ "extends TableComponent",
161
+ "extends SearchComponent",
162
+ "extends "
163
+ ],
164
+ "verify": "A typecheck of the consumer reports no TS4114 / TS2415 / TS2416 on any class that extends a DS component."
165
+ },
166
+ {
167
+ "id": "search-clear-becomes-public",
168
+ "kind": "behavior",
169
+ "old": "SearchComponent.clear",
170
+ "new": null,
171
+ "note": "CHANGED TYPE, same name: SearchComponent.clear went from `protected clear(): void` to a public `clear(): void`. For a CALLER this is purely additive — the method is now reachable, which is the point (see the ds-search.clear() entry). It breaks an OVERRIDER: a subclass that redeclared `protected clear()` no longer satisfies the base, because a derived class cannot narrow a public member to protected (TS2445-class error). ACTION: drop the `protected` keyword on your override, or rename your own method. SearchComponent.focus separately picked up an `override` modifier, which changes nothing for a consumer.",
172
+ "searchHints": [
173
+ "extends SearchComponent",
174
+ "clear()",
175
+ "protected clear",
176
+ "ds-search"
177
+ ],
178
+ "surface": "typescript",
179
+ "detect": [
180
+ "protected clear(",
181
+ "extends SearchComponent"
182
+ ],
183
+ "verify": "No SearchComponent subclass declares `protected clear()`."
184
+ },
185
+ {
186
+ "id": "time-columns-onkey-signature",
187
+ "kind": "behavior",
188
+ "old": "TimeColumnsComponent.onKey",
189
+ "new": null,
190
+ "note": "CHANGED TYPE, same name: TimeColumnsComponent.onKey's parameter list changed. It is `protected`, so no consumer calls it and templates are unaffected; it is listed because an overriding subclass now has a signature that does not match the base (TS2416). ACTION: read the current declaration in time-columns.component.ts and match it, or drop the override — the component is internal to ds-time-picker and subclassing it was never supported.",
191
+ "searchHints": [
192
+ "extends TimeColumnsComponent",
193
+ "onKey",
194
+ "ds-time-columns",
195
+ "ds-time-picker"
196
+ ],
197
+ "surface": "typescript",
198
+ "detect": [
199
+ "onKey(",
200
+ "extends TimeColumnsComponent"
201
+ ],
202
+ "verify": "No TimeColumnsComponent subclass overrides `onKey` with the old parameter list."
203
+ },
204
+ {
205
+ "id": "overlay-outside-guard-tests-the-trigger",
206
+ "kind": "behavior",
207
+ "old": "ds-select",
208
+ "new": null,
209
+ "note": "BEHAVIOUR CHANGE, narrow but test-visible. Five overlays now test their TRIGGER, not the whole host, in the outside-pointer guard: ds-select, ds-multi-select, ds-autocomplete, ds-time-picker and ds-color-picker. A press in the host's own empty width — the label, the message row, the slack beside a content-width trigger — used to be treated as INSIDE and left the panel open; it now dismisses, which is the ds-date-picker fix from 0.10.1 (MBP-225) applied to its siblings. NO ACTION in normal use: it removes a dead zone rather than adding one, and a press on the trigger itself still keeps the panel open, which is what that exception exists for (the caret, and re-focus). ACTION where a TEST or a scripted flow relied on the old dead zone — clicking a picker's LABEL while its panel is open, to focus or assert without closing it — that press now closes the panel, so the assertion after it sees a closed overlay. Retarget such a click at the trigger, or assert the closed state instead. ds-time-picker checks whichever of its three trigger boxes are present, since a range renders two.",
210
+ "searchHints": [
211
+ "ds-select",
212
+ "ds-multi-select",
213
+ "ds-autocomplete",
214
+ "ds-time-picker",
215
+ "ds-color-picker",
216
+ ".click(",
217
+ "label",
218
+ "panel"
219
+ ],
220
+ "surface": "typescript",
221
+ "detect": [
222
+ "pointerdown",
223
+ "mousedown",
224
+ "dispatchEvent"
225
+ ],
226
+ "verify": "No test asserts that a press on an overlay host's own padding (label, message row, slack beside the trigger) leaves the panel open."
227
+ },
228
+ {
229
+ "id": "stat-value-type-widened",
230
+ "kind": "behavior",
231
+ "old": "ds-stat[value]",
232
+ "new": null,
233
+ "note": "TYPE WIDENING, breaking for READERS and OVERRIDERS and invisible to writers: StatComponent.value went `string | number` to `string | number | null`. Every existing binding compiles unchanged and nothing renders differently (null renders as nothing, like the empty-string default). ACTION only where the type is written down: an explicitly typed declaration that has to accept it (`const shown: string | number = stat.value()`), a helper parameter, or a subclass override, which fails with TS2416 because the `equal` type-parameter position of InputSignal is invariant - retype to `string | number | null`, or drop the annotation. WHY it was widened: Angular's number / currency / percent / date pipes are all typed `string | null`, so `[value]=\"count | number\"` failed strictTemplates with TS2322 and pushed consumers to `count.toLocaleString('en-US')` in the template, which pins a locale instead of reading LOCALE_ID. If you have that workaround, the pipe is now the better form.",
234
+ "searchHints": [
235
+ "ds-stat",
236
+ "toLocaleString",
237
+ "StatComponent",
238
+ "[value]",
239
+ "extends StatComponent"
240
+ ],
241
+ "surface": "typescript",
242
+ "detect": [
243
+ "string | number",
244
+ "ds-stat",
245
+ "value()"
246
+ ],
247
+ "verify": "Every explicit annotation that reads a `ds-stat` value accepts null."
248
+ },
249
+ {
250
+ "id": "field-message-state-icons",
251
+ "kind": "behavior",
252
+ "old": "ds-field-message",
253
+ "new": null,
254
+ "note": "APPEARANCE CHANGE on every field that shows a state: the message line now leads with a glyph for `error` (icon `error`), `warning` (`warn`) and `success` (`success`). The `hint` line is unchanged - no glyph - because it is the resting text rather than a state, and it is the majority of rows on a real form. NO CODE ACTION for anyone who wants it. THE ONE LINE BACK, if you do not: `provideDsConfig({ field: { stateIcons: false } })` at the root. Per state instead of all: `stateIcons: { warning: false }` turns one off, `stateIcons: { hint: 'info' }` turns the hint line on, and an IconName replaces a glyph rather than removing it - each key independent. Per FIELD: every one of the fifteen field components gained a `messageIcon` input which wins over the config - `[messageIcon]=\"false\"` drops the glyph on that field alone, `messageIcon=\"info\"` replaces it. TWO NEW CSS HOOKS: --ds-field-message-icon-gap and --ds-field-message-icon-offset. ALSO CHANGED in the same row: `align-items` went `center` to `flex-start`, so a message that WRAPS keeps its glyph beside the first line instead of centred on the block - if you had compensated for the old centring with your own margin on that row, drop it. The glyph size is not a token (ds-icon takes a number): it is 14px, matching --icon-sm.",
255
+ "searchHints": [
256
+ "ds-field-message",
257
+ "--ds-field-message",
258
+ "stateIcons",
259
+ "messageIcon",
260
+ "field-message"
261
+ ],
262
+ "surface": [
263
+ "template",
264
+ "style"
265
+ ],
266
+ "verify": "Every field showing error / warning / success renders a 14px glyph before its message text and hint rows render none; an app that set stateIcons:false shows no glyph on any state; a field with [messageIcon]=\"false\" shows none while its neighbours do."
267
+ },
268
+ {
269
+ "id": "search-drops-the-message-inputs",
270
+ "kind": "removed-api",
271
+ "old": "ds-search[hint]",
272
+ "new": null,
273
+ "surface": [
274
+ "template",
275
+ "typescript"
276
+ ],
277
+ "note": "REMOVED from ds-search, which never rendered any of them: hint, error, warning, errors, invalid, touched, reserveMessage, messageIcon (and the reserveMessageResolved readback). They arrived by inheritance when search gained form binding - it extended DsControlValueAccessor, which sits on DsFieldBase - so the API reference advertised eight inputs whose values nothing read. ACTION: delete the binding. It used to compile and do nothing; it is now a template type error, which is the whole point of the change. If the field genuinely needs a label or a validation line, use ds-input - ds-search is a toolbar filter and deliberately has no message row. NOT affected: value, disabled, hidden, size, debounce, clearable, placeholder, shortcut, showIcon, ariaLabel, and the CVA itself - formControl / formControlName / ngModel / signal forms all still bind. INVISIBLE TO class-surface, recorded by hand: the tool reads per-file declarations, and these were never declared in search.component.ts.",
278
+ "verify": "Binding hint/error/warning/errors/invalid/touched/reserveMessage/messageIcon on a ds-search fails to compile, while formControl binding and the disabled surface still work.",
279
+ "searchHints": [
280
+ "ds-search",
281
+ "<ds-search",
282
+ "error=",
283
+ "hint=",
284
+ "reserveMessage",
285
+ "messageIcon"
286
+ ]
287
+ },
288
+ {
289
+ "id": "one-focus-ring-per-field",
290
+ "kind": "behavior",
291
+ "old": "ds-search, ds-autocomplete, ds-date-picker, ds-number-stepper, ds-field-group",
292
+ "new": null,
293
+ "surface": "style",
294
+ "note": "APPEARANCE FIX, no action: a focused field drew TWO rings - a tight one around the inner control (the universal :where(:focus-visible) box-shadow shipped in 0.10.0) and the halo the shell paints on :focus-within. The inner one is now suppressed where the shell speaks for the control. ACTION only if you wrote a workaround: a rule that killed one of the two rings (box-shadow: none on an inner input, or a re-declared --ds-field-focus-shadow meant to hide the doubling) can go. Deliberately NOT suppressed: a ds-number-stepper step button and a chip close button keep their own ring, because both are tabindex=0 tab stops that the shell halo cannot distinguish.",
295
+ "verify": "A focused ds-search, ds-autocomplete, ds-date-picker or ds-input inside a ds-field-group shows exactly one ring; a step button inside ds-number-stepper still shows its own when tabbed to.",
296
+ "searchHints": [
297
+ "--ds-field-focus-shadow",
298
+ "--ds-control-focus-shadow",
299
+ "box-shadow: none",
300
+ "focus-visible",
301
+ "ds-field-group"
302
+ ]
303
+ },
304
+ {
305
+ "id": "clipped-labels-keep-their-descenders",
306
+ "kind": "behavior",
307
+ "old": ".option-label, .cell-clip, .crumb, ds-breadcrumbs .label",
308
+ "new": null,
309
+ "surface": "style",
310
+ "note": "APPEARANCE FIX, no action, no geometry change (option row 30px, multi-select 36px, table row 38px are all unchanged): every clipped label sat in a line-height:1 box with no padding, so 2.13px above the cap line and 1.47px below the baseline were cut - MBP-245. They now use overflow: clip with a --space-1 clip margin. ACTION only if you worked around it: a padding-block or line-height override added to an option label, a table cell clip or a breadcrumb to get the descenders back can go. NOTE for a consumer with the same shape in their own CSS: overflow: clip keeps text-overflow: ellipsis working and keeps scrollWidth > clientWidth reporting true, both checked in Chromium, so a clip-detection test does not need changing. Where overflow-clip-margin is unsupported, clip degrades to exactly the old shave.",
311
+ "verify": "An option list, a clipped table cell and a breadcrumb render full descenders (the tail of a g is complete) at unchanged row heights.",
312
+ "searchHints": [
313
+ "option-label",
314
+ "cell-clip",
315
+ "overflow: hidden",
316
+ "line-height: 1",
317
+ "text-overflow"
318
+ ]
319
+ }
320
+ ],
321
+ "informational": [
322
+ "ds-table: `TableRowAction` gained `hidden?: (row) => boolean` and `disabledReason?: string | ((row) => string)`. Purely additive -- an existing config behaves exactly as before. Reach for `hidden` where an action does not APPLY to a row rather than `disabled`, which greys an item that is always present; a row with every item hidden now renders no kebab instead of an empty menu.",
323
+ "ds-menu-item: new `description` input renders a standing second line and wires `aria-describedby`. If you hand-rolled that line by projecting your own span into the item, move it to the input -- yours lands INSIDE the accessible name, the input's does not.",
324
+ "ds-search: `clear()` is now public. A host-owned Clear button should call it rather than writing '' into `value`, which does not cancel an armed debounce when the text already matches what the control last pushed.",
325
+ "ds-multi-select: its panel now honours `--ds-dropdown-panel-radius` (it was hardcoded at 8px). If you set that token and wondered why one of the three connected panels ignored it, this is why -- no action needed beyond re-checking the value looks right on all three.",
326
+ "ds-search joins both form systems: NG_VALUE_ACCESSOR + DsControlValueAccessor, so [(ngModel)], formControlName and a signal form now bind it, and a new `disabled` input folds together with the form's own disabled state (the shell paints the disabled surface, which it never did). Its own [(value)] is unchanged. Deliberately NO label and no message row - a toolbar filter is not a validated field.",
327
+ "ds-menu: new --ds-menu-radius, defaulting to --radius-md, which is what the component hardcoded. Nothing moves. Inside a ds-popover the menu still clips to --ds-menu-clip-radius, published by the popover.",
328
+ "maxVisibleChips gained an 'all' mode on ds-autocomplete and ds-multi-select - render every chip, no measuring. Additive on its own; the actionable half is that null no longer means that (see max-visible-chips-null-is-unset-*).",
329
+ "ds-button variant=\"tonal\": the disabled label now uses the same 40% mix toward --surface-default as ghost / text / outline, instead of the shared oklch(from accent 70% ...) recipe. Visual only, no action. It fixes the dark theme, where the old recipe left the disabled label 1.11:1 from the enabled one (a hue going grey and nothing else); the state gap is now 2.90:1 dark and 3.39:1 light, and the label keeps its hue. --ds-button-label-color-disabled still overrides it.",
330
+ "ds-table: TableColumn gained `interactive?: boolean`. The marked column's cell takes --ds-table-cell-link-color (default --accent) and --ds-table-cell-link-decoration (default underline) while its row is hovered, on a rowInteractive table only. Purely additive - an existing column config renders exactly as before. Reach for it on the cell whose TEXT names what the row opens; the row tint says the row is clickable and nothing else said which text was the target.",
331
+ "ds fields on the SIGNAL FORMS path: they threw once per field (NgControl bridge has no events stream) and then displayed the first validation failure forever, because the frozen snapshot was the fallback whenever live errors went empty. Fixed - the NgControl path now bows out when it has no live stream. No consumer action: if you bind [field] on a DS control, upgrade and the console noise and the stale message both go. Reactive and template-driven forms are unchanged.",
332
+ "DS_CONFIG: provideDsConfig() must be called ONCE per injector. Two calls in the same `providers` array do not merge - both resolve their parent with skipSelf, so the later wins and the earlier is silently lost. Merging happens across injector LEVELS (a route or component inheriting the app's config), not within one array. Documented on the function after it bit us in our own docs app."
333
+ ],
334
+ "deleteList": [
335
+ {
336
+ "id": "menu-item-hand-rolled-second-line",
337
+ "surface": [
338
+ "template",
339
+ "style"
340
+ ],
341
+ "find": [
342
+ "ds-menu-item",
343
+ "max-width: 14rem"
344
+ ],
345
+ "why": "A projected span plus a width cap standing in for a second line on a menu item, usually with no aria-describedby.",
346
+ "replaceWith": "the `description` input, capped by --ds-menu-item-description-max-width"
347
+ },
348
+ {
349
+ "id": "focus-ring-clipping-workaround",
350
+ "surface": "style",
351
+ "find": [
352
+ "overflow: visible",
353
+ "inset 0 0 0 2px"
354
+ ],
355
+ "why": "overflow forced back onto an element that needs to clip, or a hand-rolled inset shadow standing in for the focus ring the clip ate.",
356
+ "replaceWith": "data-focus=\"inset\" on the clipping element"
357
+ },
358
+ {
359
+ "id": "multi-select-panel-radius-override",
360
+ "surface": "style",
361
+ "find": [
362
+ "ds-multi-select .panel",
363
+ "--ds-multi-select-panel"
364
+ ],
365
+ "why": "The panel radius reached two of the three dropdowns, so the third was retuned by hand.",
366
+ "replaceWith": "--ds-dropdown-panel-radius, which now reaches all three"
367
+ },
368
+ {
369
+ "id": "search-clear-timer",
370
+ "surface": "typescript",
371
+ "find": [
372
+ "setTimeout",
373
+ "ds-search"
374
+ ],
375
+ "why": "A timer around a Clear button, or a value written twice to make the debounce let go.",
376
+ "replaceWith": "clear()"
377
+ },
378
+ {
379
+ "id": "hand-rolled-config-fallback",
380
+ "surface": "typescript",
381
+ "find": [
382
+ "?? config.control?.size",
383
+ "config.control?.size"
384
+ ],
385
+ "why": "A copy of the DS_CONFIG fallback chain in the host, written when the resolver was protected.",
386
+ "replaceWith": "the component's now-public *Resolved readback"
387
+ },
388
+ {
389
+ "id": "sidenav-active-wash-override",
390
+ "surface": "style",
391
+ "find": [
392
+ "--ds-sidenav-item-bg-color-active"
393
+ ],
394
+ "why": "A wash replacing the old solid active pill is what the default draws now.",
395
+ "replaceWith": "nothing - compare the override with the new default and drop it if they agree"
396
+ },
397
+ {
398
+ "id": "sidenav-rail-hidden-by-css",
399
+ "surface": "style",
400
+ "find": [
401
+ "--ds-sidenav-item-rail: transparent",
402
+ "--ds-sidenav-item-rail"
403
+ ],
404
+ "why": "Hiding the active rail through a token or a ::ng-deep shadow reset.",
405
+ "replaceWith": "[rail]=\"false\" on ds-sidenav"
406
+ },
407
+ {
408
+ "id": "menu-radius-deep-rule",
409
+ "surface": "style",
410
+ "find": [
411
+ "ds-menu",
412
+ "border-radius"
413
+ ],
414
+ "why": "A ::ng-deep radius rule on a bare ds-menu, written when the panel had no hook.",
415
+ "replaceWith": "--ds-menu-radius"
416
+ },
417
+ {
418
+ "id": "tonal-disabled-label-pin",
419
+ "surface": "style",
420
+ "find": [
421
+ "--ds-button-label-color-disabled"
422
+ ],
423
+ "why": "Pinned to make a tonal button's disabled state visible, most often in the dark theme only.",
424
+ "replaceWith": "the default disabled-label recipe"
425
+ },
426
+ {
427
+ "id": "stat-value-hand-formatting",
428
+ "surface": "template",
429
+ "find": [
430
+ "toLocaleString('en-US')",
431
+ "toLocaleString("
432
+ ],
433
+ "why": "Hand-rolled formatting inside a ds-stat binding, because `[value]=\"count | number\"` did not typecheck while value was `string | number`.",
434
+ "replaceWith": "the number pipe, which reads LOCALE_ID instead of a pinned locale"
435
+ },
436
+ {
437
+ "id": "table-cell-link-deep-rule",
438
+ "surface": "style",
439
+ "find": [
440
+ "ds-table tr:hover",
441
+ "::ng-deep ds-table"
442
+ ],
443
+ "why": "A deep hover rule making one cell read as the row's link target.",
444
+ "replaceWith": "interactive: true on that column, retuned with --ds-table-cell-link-color and --ds-table-cell-link-decoration"
445
+ },
446
+ {
447
+ "id": "field-state-icon-hand-rolled",
448
+ "surface": [
449
+ "template",
450
+ "style"
451
+ ],
452
+ "find": [
453
+ "ds-icon",
454
+ "field-message",
455
+ "align-items: center"
456
+ ],
457
+ "why": "A glyph rendered by hand beside a field's error or warning text, or a margin nudge added to line one up against the old centred message row.",
458
+ "replaceWith": "the built-in state glyph (error / warning / success carry one now), retuned through DS_CONFIG.field.stateIcons or messageIcon, with --ds-field-message-icon-gap / -offset for the spacing"
459
+ },
460
+ {
461
+ "id": "double-focus-ring-workaround",
462
+ "surface": "style",
463
+ "find": [
464
+ "box-shadow: none",
465
+ "--ds-field-focus-shadow"
466
+ ],
467
+ "why": "A rule that killed one of the two focus rings a field used to paint - on an inner input, or by re-declaring the field focus shadow.",
468
+ "replaceWith": "nothing: the field paints one ring now"
469
+ },
470
+ {
471
+ "id": "descender-clip-workaround",
472
+ "surface": "style",
473
+ "find": [
474
+ "padding-block",
475
+ "line-height",
476
+ "option-label"
477
+ ],
478
+ "why": "A padding or line-height override added to an option label, a clipped table cell or a breadcrumb to stop the descenders being shaved.",
479
+ "replaceWith": "nothing: the clip carries a --space-1 margin now, at the same row height"
480
+ }
481
+ ]
482
+ }
@@ -0,0 +1,73 @@
1
+ {
2
+ "version": "0.10.3",
3
+ "items": [
4
+ {
5
+ "id": "one-focus-ring-per-field-input-textarea",
6
+ "kind": "behavior",
7
+ "old": "ds-input, ds-textarea",
8
+ "new": null,
9
+ "surface": "style",
10
+ "note": "APPEARANCE FIX, no action: the two shells 0.10.2's one-focus-ring-per-field pass missed. A focused ds-input or ds-textarea drew TWO rings - the 4px control ring the universal :where(:focus-visible) rule puts on the inner input/textarea, plus the 3px field halo the box paints on :focus-within. The inner one is now suppressed. ACTION only if you wrote a workaround: a rule that killed one of the two (box-shadow: none on an inner input, a re-declared --ds-input-focus-shadow meant to hide the doubling) can go. Deliberately NOT suppressed: the clear button and the password toggle inside the same box keep their own ring, because both are real tab stops the box halo cannot distinguish.",
11
+ "verify": "Tab into a ds-input and a ds-textarea: each shows exactly one ring, the halo around the box. Tab on to the clear button or password toggle inside that field and a second, tighter ring appears on the button - that one is intended.",
12
+ "searchHints": [
13
+ "--ds-input-focus-shadow",
14
+ "--ds-field-focus-shadow",
15
+ "--ds-control-focus-shadow",
16
+ "box-shadow: none",
17
+ "focus-visible"
18
+ ]
19
+ },
20
+ {
21
+ "id": "search-clear-button-focus-indicator",
22
+ "kind": "behavior",
23
+ "old": "ds-search",
24
+ "new": null,
25
+ "surface": "style",
26
+ "note": "ACCESSIBILITY FIX, no action: 0.10.2's ring fix silenced the base focus indicator with a shell-wide reset, which also hit .search-clear - a tabindex=0 tab stop. Tabbing from the input to the clear button changed nothing on screen (box-shadow, outline, border, background and colour all identical), so a keyboard user could not tell the button had focus: a WCAG 2.4.7 failure. Every shell now names the single control it silences, so tab stops inside a field box keep their own ring. ACTION only if you re-added a ring to that button yourself - that rule can go.",
27
+ "verify": "Type into a ds-search so the clear button appears, then Tab: the × shows its own ring on top of the field halo. Same for a chip close button in ds-autocomplete or ds-multi-select, and for the arrows in ds-number-stepper.",
28
+ "searchHints": [
29
+ "search-clear",
30
+ "ds-search",
31
+ "focus-visible",
32
+ "box-shadow"
33
+ ]
34
+ },
35
+ {
36
+ "id": "portaled-panel-focus-indicator",
37
+ "kind": "behavior",
38
+ "old": "ds-date-picker, ds-time-picker",
39
+ "new": null,
40
+ "surface": "style",
41
+ "note": "ACCESSIBILITY FIX, no action: two tabbable buttons inside the portaled panels had no focus indicator at all, and one panel had square corners. Both read a private --_*-focus-shadow token declared on :host while the panel is portaled out of the host by the CDK, so the var() resolved to nothing and box-shadow fell back to its initial value none - with outline: none beside it, nothing was left. ds-time-picker's panel border-radius read the same way and fell back to 0. ACTION only if you worked around either: a rule adding a ring to .period-trigger or .time-action, or a border-radius forced onto .time-panel, can go.",
42
+ "verify": "Open the ds-date-picker calendar and Tab to the month/year header: it shows a focus ring. Open the ds-time-picker panel and Tab to its action button: same. The time-picker panel has rounded corners.",
43
+ "searchHints": [
44
+ "period-trigger",
45
+ "time-action",
46
+ "time-panel",
47
+ "--ds-date-picker-focus-shadow",
48
+ "--ds-time-picker-focus-shadow",
49
+ "--ds-time-picker-panel-radius"
50
+ ]
51
+ }
52
+ ],
53
+ "informational": [
54
+ "The shell list in styles/_focus.scss is now maintained from a measurement, not from a read of the code: it had been wrong for two releases. If you add a component that paints its own ring on :focus-within, suppress the base rule on the control it speaks for - `outline: 0` cannot do it, because the base indicator is a box-shadow.",
55
+ "Two authoring mixins are now documented for consumers building their own composite controls: `focus.owns-the-focus-ring($control)` in styles/focus, and `text-clip.single-line-ellipsis` in styles/text-clip. Both are opt-in - no existing code changes.",
56
+ "A private --_* token declared on :host does not reach a CDK-portaled panel, and an unresolvable var() silently becomes the property's initial value - none for box-shadow, 0 for border-radius. If you style a DS panel from your own CSS, read the PUBLIC --ds-* token there, not the private one.",
57
+ "Eleven public tokens were always overridable but never reached the token reference, because the extractor searched for the literal `var(--ds-` and a resolver wrapped across lines put a newline inside it: --ds-container-pad-x, --ds-multi-select-border-color (+-focus), --ds-segmented-selected-bg-color / -label-color / --ds-segmented-radius, --ds-time-picker-option-bg-color-selected / -text-color-selected / -bg-color-hover, --ds-time-picker-trigger-bg-color / -border / -color. Nothing changed in the components - if you hand-rolled around one of these because it looked unsupported, the override works and the workaround can go."
58
+ ],
59
+ "deleteList": [
60
+ {
61
+ "id": "input-double-ring-workaround",
62
+ "surface": "style",
63
+ "find": [
64
+ "ds-input input",
65
+ "ds-textarea textarea",
66
+ "--ds-input-focus-shadow",
67
+ "box-shadow: none"
68
+ ],
69
+ "why": "A rule killing one of the two focus rings a ds-input or ds-textarea used to paint - typically box-shadow: none on the inner input, or --ds-input-focus-shadow re-declared as none to hide the doubling.",
70
+ "replaceWith": "nothing - the component now paints one ring on its own"
71
+ }
72
+ ]
73
+ }