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

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.
Files changed (58) hide show
  1. package/CHANGELOG.md +1376 -904
  2. package/components.md +61 -30
  3. package/design-system.md +18 -18
  4. package/fesm2022/ids-group-ltd-ids-design-system.mjs +992 -486
  5. package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
  6. package/migrations/0.1.0.json +2 -1
  7. package/migrations/0.10.0.json +219 -42
  8. package/migrations/0.10.1.json +50 -13
  9. package/migrations/0.10.2.json +90 -24
  10. package/migrations/0.10.3.json +22 -5
  11. package/migrations/0.11.0.json +216 -0
  12. package/migrations/0.11.1.json +305 -0
  13. package/migrations/0.2.0.json +22 -9
  14. package/migrations/0.2.1.json +2 -1
  15. package/migrations/0.2.2.json +3 -2
  16. package/migrations/0.3.0.json +16 -10
  17. package/migrations/0.4.0.json +38 -14
  18. package/migrations/0.5.0.json +49 -25
  19. package/migrations/0.5.1/badge-statuses.md +1 -3
  20. package/migrations/0.5.1.json +75 -33
  21. package/migrations/0.6.0.json +6 -2
  22. package/migrations/0.6.1.json +19 -1
  23. package/migrations/0.6.2.json +3 -1
  24. package/migrations/0.6.3.json +13 -4
  25. package/migrations/0.7.0.json +45 -26
  26. package/migrations/0.7.1.json +58 -20
  27. package/migrations/0.8.0.json +53 -15
  28. package/migrations/0.9.0.json +147 -27
  29. package/migrations/0.9.1.json +4 -3
  30. package/migrations/README.md +34 -52
  31. package/package.json +2 -1
  32. package/styles/_dropdown-overlay.scss +35 -13
  33. package/styles/_ds-color.scss +3 -3
  34. package/styles/_field-box.scss +2 -6
  35. package/styles/_field-label.scss +5 -10
  36. package/styles/_field-state.scss +3 -2
  37. package/styles/_focus.scss +0 -2
  38. package/styles/_layout-utils.scss +2 -2
  39. package/styles/_link.scss +1 -2
  40. package/styles/_overlay-motion.scss +2 -4
  41. package/styles/_press.scss +3 -5
  42. package/styles/_reset.scss +0 -1
  43. package/styles/_scrollbar.scss +1 -3
  44. package/styles/_status.scss +1 -2
  45. package/styles/_surface-motion.scss +3 -4
  46. package/styles/_text-clip.scss +1 -1
  47. package/styles/_theme-activation.scss +1 -1
  48. package/styles/_tokens-charts.scss +1 -3
  49. package/styles/_tokens.scss +4 -3
  50. package/styles/_typography.scss +2 -2
  51. package/themes/README.md +3 -3
  52. package/themes/_base-palette.scss +2 -2
  53. package/themes/_semantic.scss +2 -2
  54. package/themes/dark/_palette.scss +1 -2
  55. package/themes/light/_palette.scss +1 -1
  56. package/themes/light/_theme.scss +1 -1
  57. package/types/ids-group-ltd-ids-design-system.d.ts +403 -108
  58. package/migrations/AUTHORING.md +0 -273
@@ -6,7 +6,8 @@
6
6
  "kind": "input-rename",
7
7
  "old": "ds-modal[danger]",
8
8
  "new": "error",
9
- "note": "Status vocab unified to DsStatus (info|success|warning|error). Boolean input [danger] -> [error] (also static danger=\"...\" -> error=\"...\"). Default value unchanged.",
9
+ "action": "Rename the input `[danger]` to `[error]` on ds-modal, and `danger` to `error` as a static attribute.",
10
+ "note": "Part of one status vocabulary across the library: `error` is the word every component uses now.",
10
11
  "searchHints": [
11
12
  "<ds-modal",
12
13
  "[danger]",
@@ -19,7 +20,7 @@
19
20
  "kind": "input-rename",
20
21
  "old": "ds-modal-card[danger]",
21
22
  "new": "error",
22
- "note": "Same danger -> error boolean-input rename on ds-modal-card.",
23
+ "action": "Rename `[danger]` to `[error]` on ds-modal-card.",
23
24
  "searchHints": [
24
25
  "<ds-modal-card",
25
26
  "[danger]",
@@ -32,7 +33,7 @@
32
33
  "kind": "input-rename",
33
34
  "old": "ds-menu-item[danger]",
34
35
  "new": "error",
35
- "note": "Same danger -> error boolean-input rename on ds-menu-item.",
36
+ "action": "Rename `[danger]` to `[error]` on ds-menu-item.",
36
37
  "searchHints": [
37
38
  "<ds-menu-item",
38
39
  "[danger]",
@@ -45,7 +46,9 @@
45
46
  "kind": "value-remap",
46
47
  "old": "ds-stat[variant]",
47
48
  "new": null,
48
- "note": "ds-stat variant value 'danger' -> 'error'. Other variant values unchanged (absent from map — leave them).",
49
+ "action": "Replace `variant=\"danger\"` with `variant=\"error\"` on ds-stat.",
50
+ "appliesWhen": "Other variant values are unchanged and absent from the map — leave them.",
51
+ "note": "Part of one status vocabulary across the library: every component says error where some used to say danger.",
49
52
  "searchHints": [
50
53
  "<ds-stat",
51
54
  "variant=\"",
@@ -54,14 +57,18 @@
54
57
  "map": {
55
58
  "danger": "variant=\"error\""
56
59
  },
57
- "surface": "template"
60
+ "surface": "template",
61
+ "verify": "No ds-stat binds variant=\"danger\". Every stat that used to be danger renders in the error colour, and stats on other variant values are untouched."
58
62
  },
59
63
  {
60
64
  "id": "progress-variant-remap",
61
65
  "kind": "value-remap",
62
66
  "old": "ds-progress[variant]",
63
67
  "new": null,
64
- "note": "Two changes on ds-progress[variant]: 'warn' -> 'warning'; and 'indeterminate' is no longer a variant value — it becomes the boolean [indeterminate] input, so variant=\"indeterminate\" -> the bare indeterminate attribute (a bar can now be e.g. success-coloured AND indeterminate). ProgressVariant is now 'default' | 'success' | 'warning' | 'error' — TS references to the removed 'warn'/'indeterminate' members update accordingly. 'success'/'error'/'default' unchanged (absent from map).",
68
+ "action": "Rename `variant=\"warn\"` to `variant=\"warning\"`, and move `variant=\"indeterminate\"` to the bare `indeterminate` attribute. Update TS references to the removed `ProgressVariant` members; the union is `default | success | warning | error` now.",
69
+ "appliesWhen": "success, error and default are unchanged and absent from the map.",
70
+ "pitfall": "`indeterminate` was a variant VALUE and is a boolean input now, so the two are no longer mutually exclusive — a bar can be success-coloured and indeterminate at once. Leaving `variant=\"indeterminate\"` in place gives an unknown value, which resolves to the default colour and a determinate bar.",
71
+ "note": "Two axes were conflated in one input. Colour and progress state are independent, so the state moved out to its own boolean and the colour vocabulary joined the library-wide status words.",
65
72
  "searchHints": [
66
73
  "<ds-progress",
67
74
  "variant=\"",
@@ -72,14 +79,20 @@
72
79
  "warn": "variant=\"warning\"",
73
80
  "indeterminate": "indeterminate"
74
81
  },
75
- "surface": "template"
82
+ "surface": [
83
+ "template",
84
+ "style",
85
+ "typescript"
86
+ ],
87
+ "verify": "No ds-progress binds `variant=\"warn\"` or `variant=\"indeterminate\"`: the colour vocabulary is `default | success | warning | error`, and the indeterminate state is the bare `indeterminate` attribute. Nothing is typed with a removed ProgressVariant member."
76
88
  },
77
89
  {
78
90
  "id": "modal-confirm-tone-danger-remap",
79
91
  "kind": "behavior",
80
92
  "old": "ModalConfirmTone",
81
93
  "new": null,
82
- "note": "ModalConfirmTone value 'danger' -> 'error'. Update ModalService.confirm({ tone: 'danger' }) -> { tone: 'error' } and any TS typed with ModalConfirmTone.",
94
+ "action": "Replace the `'danger'` tone with `'error'` in ModalService.confirm() calls and anything typed with ModalConfirmTone.",
95
+ "note": "Same status vocabulary as the component inputs.",
83
96
  "searchHints": [
84
97
  "ModalConfirmTone",
85
98
  "tone:",
@@ -97,7 +110,8 @@
97
110
  "kind": "behavior",
98
111
  "old": "SplitButtonItem",
99
112
  "new": null,
100
- "note": "SplitButtonItem object property `danger` renamed to `error`. Update item literals ({ danger: true } -> { error: true }) and any TS typed with SplitButtonItem.",
113
+ "action": "Rename the `danger` property on a SplitButtonItem to `error`.",
114
+ "note": "Same status vocabulary, on the item object rather than an input.",
101
115
  "searchHints": [
102
116
  "SplitButtonItem",
103
117
  "danger:"
@@ -114,7 +128,7 @@
114
128
  "kind": "token-rename",
115
129
  "old": "--ds-menu-item-danger-label-color",
116
130
  "new": "--ds-menu-item-error-label-color",
117
- "note": "Public token renamed in lockstep with [danger] -> [error]. CSS property and default unchanged.",
131
+ "action": "Replace `--ds-menu-item-danger-label-color` with `--ds-menu-item-error-label-color`.",
118
132
  "searchHints": [
119
133
  "--ds-menu-item-danger-label-color"
120
134
  ],
@@ -125,7 +139,10 @@
125
139
  "kind": "class-rename",
126
140
  "old": "ds-modal .danger",
127
141
  "new": ".error",
128
- "note": "The status-vocabulary rename also renamed the class the card puts on its root: [danger] used to emit `danger`, [error] now emits `error`. The input-rename item fixes the BINDING; a consumer stylesheet that keys off the class needs this one, and nothing in the binding rename would find it. Scope strictly to selectors under ds-modal / ds-modal-card.",
142
+ "action": "Rename `.danger` to `.error` in selectors scoped under ds-modal and ds-modal-card.",
143
+ "appliesWhen": "Only if a stylesheet of yours keys off the class the component puts on its root.",
144
+ "pitfall": "The input rename fixes the BINDING and nothing about it reaches your stylesheet, so a search for `danger` in templates comes back clean while the CSS keyed on `.danger` quietly stops matching. Two artifacts, two items — this is the second one.",
145
+ "note": "The root class follows the input: `[danger]` used to emit `danger`, `[error]` emits `error`.",
129
146
  "searchHints": [
130
147
  "ds-modal",
131
148
  "ds-modal-card",
@@ -139,7 +156,8 @@
139
156
  "kind": "class-rename",
140
157
  "old": "ds-menu-item .danger",
141
158
  "new": ".error",
142
- "note": "Same rename on ds-menu-item: the host used to carry `danger`, it now carries `error`. Consumer STYLING only.",
159
+ "action": "Rename `.danger` to `.error` in selectors scoped under ds-menu-item.",
160
+ "appliesWhen": "Only if a stylesheet of yours keys off the class rather than the input.",
143
161
  "searchHints": [
144
162
  "ds-menu-item",
145
163
  ".danger"
@@ -151,7 +169,8 @@
151
169
  "kind": "class-rename",
152
170
  "old": "ds-stat .danger",
153
171
  "new": ".error",
154
- "note": "ds-stat's variant value moved danger -> error, and the host class follows it (host binding [class.error]). Consumer STYLING only; the value-remap item covers the binding.",
172
+ "action": "Rename `.danger` to `.error` in selectors scoped under ds-stat.",
173
+ "appliesWhen": "Only if a stylesheet of yours keys off the class rather than the input.",
155
174
  "searchHints": [
156
175
  "ds-stat",
157
176
  ".danger"
@@ -163,7 +182,8 @@
163
182
  "kind": "class-rename",
164
183
  "old": "ds-progress .danger",
165
184
  "new": ".error",
166
- "note": "Same as ds-stat: variant value danger -> error with a matching host class. Consumer STYLING only.",
185
+ "action": "Rename `.danger` to `.error` in selectors scoped under ds-progress.",
186
+ "appliesWhen": "Only if a stylesheet of yours keys off the class rather than the input.",
167
187
  "searchHints": [
168
188
  "ds-progress",
169
189
  ".danger"
@@ -175,7 +195,7 @@
175
195
  "kind": "token-rename",
176
196
  "old": "--ds-progress-bar-color-warn",
177
197
  "new": "--ds-progress-bar-color-warning",
178
- "note": "Public token renamed in lockstep with the 'warn' -> 'warning' value. CSS property and default unchanged.",
198
+ "action": "Replace `--ds-progress-bar-color-warn` with `--ds-progress-bar-color-warning`.",
179
199
  "searchHints": [
180
200
  "--ds-progress-bar-color-warn"
181
201
  ],
@@ -186,7 +206,7 @@
186
206
  "kind": "output-rename",
187
207
  "old": "ds-alert[dismissed]",
188
208
  "new": "closed",
189
- "note": "Dismissal event unified to (closed): (dismissed) -> (closed) on ds-alert.",
209
+ "action": "Rename `(dismissed)` to `(closed)` on ds-alert.",
190
210
  "searchHints": [
191
211
  "<ds-alert",
192
212
  "(dismissed)"
@@ -198,7 +218,7 @@
198
218
  "kind": "output-rename",
199
219
  "old": "ds-banner[dismissed]",
200
220
  "new": "closed",
201
- "note": "(dismissed) -> (closed) on ds-banner.",
221
+ "action": "Rename `(dismissed)` to `(closed)` on ds-banner.",
202
222
  "searchHints": [
203
223
  "<ds-banner",
204
224
  "(dismissed)"
@@ -210,7 +230,7 @@
210
230
  "kind": "output-rename",
211
231
  "old": "ds-toast[dismissed]",
212
232
  "new": "closed",
213
- "note": "(dismissed) -> (closed) on ds-toast.",
233
+ "action": "Rename `(dismissed)` to `(closed)` on ds-toast.",
214
234
  "searchHints": [
215
235
  "<ds-toast",
216
236
  "(dismissed)"
@@ -222,7 +242,7 @@
222
242
  "kind": "output-rename",
223
243
  "old": "ds-table[rowClick]",
224
244
  "new": "rowClicked",
225
- "note": "Action event made past-tense: (rowClick) -> (rowClicked) on ds-table.",
245
+ "action": "Rename `(rowClick)` to `(rowClicked)` on ds-table.",
226
246
  "searchHints": [
227
247
  "<ds-table",
228
248
  "(rowClick)"
@@ -234,7 +254,7 @@
234
254
  "kind": "output-rename",
235
255
  "old": "ds-stepper[stepClick]",
236
256
  "new": "stepClicked",
237
- "note": "(stepClick) -> (stepClicked) on ds-stepper.",
257
+ "action": "Rename `(stepClick)` to `(stepClicked)` on ds-stepper.",
238
258
  "searchHints": [
239
259
  "<ds-stepper",
240
260
  "(stepClick)"
@@ -246,7 +266,7 @@
246
266
  "kind": "output-rename",
247
267
  "old": "ds-calendar-day[daySelect]",
248
268
  "new": "daySelected",
249
- "note": "(daySelect) -> (daySelected) on ds-calendar-day.",
269
+ "action": "Rename `(daySelect)` to `(daySelected)` on ds-calendar-day.",
250
270
  "searchHints": [
251
271
  "<ds-calendar-day",
252
272
  "(daySelect)"
@@ -258,7 +278,7 @@
258
278
  "kind": "output-rename",
259
279
  "old": "ds-tabs[tabClose]",
260
280
  "new": "tabClosed",
261
- "note": "(tabClose) -> (tabClosed) on ds-tabs.",
281
+ "action": "Rename `(tabClose)` to `(tabClosed)` on ds-tabs.",
262
282
  "searchHints": [
263
283
  "<ds-tabs",
264
284
  "(tabClose)"
@@ -270,7 +290,7 @@
270
290
  "kind": "output-rename",
271
291
  "old": "ds-tree[nodeSelect]",
272
292
  "new": "nodeSelected",
273
- "note": "(nodeSelect) -> (nodeSelected) on ds-tree.",
293
+ "action": "Rename `(nodeSelect)` to `(nodeSelected)` on ds-tree.",
274
294
  "searchHints": [
275
295
  "<ds-tree",
276
296
  "(nodeSelect)"
@@ -282,7 +302,7 @@
282
302
  "kind": "output-rename",
283
303
  "old": "ds-split-button[itemSelect]",
284
304
  "new": "itemSelected",
285
- "note": "(itemSelect) -> (itemSelected) on ds-split-button.",
305
+ "action": "Rename `(itemSelect)` to `(itemSelected)` on ds-split-button.",
286
306
  "searchHints": [
287
307
  "<ds-split-button",
288
308
  "(itemSelect)"
@@ -294,7 +314,9 @@
294
314
  "kind": "behavior",
295
315
  "old": "ds-drawer",
296
316
  "new": null,
297
- "note": "title is now REQUIRED on ds-drawer, ds-bottom-sheet, and ds-accordion-item (it is the component's accessible name / disclosure-button label). Add a [title]/title if any instance is missing one. ds-page-header title is now OPTIONAL (plain <h1>) — no action there.",
317
+ "action": "Add a `title` to every ds-drawer, ds-bottom-sheet and ds-accordion-item that lacks one — it is the accessible name, and on the accordion the disclosure-button label.",
318
+ "appliesWhen": "ds-page-header went the other way: its title is optional now, a plain h1. Nothing to do there.",
319
+ "note": "These three are named by their title: it is the accessible name a screen reader announces, and on the accordion it is also the disclosure-button label. Without one the control announces nothing.",
298
320
  "searchHints": [
299
321
  "<ds-drawer",
300
322
  "<ds-bottom-sheet",
@@ -313,20 +335,30 @@
313
335
  "kind": "input-rename",
314
336
  "old": "ds-badge[variant]",
315
337
  "new": "status",
316
- "note": "ds-badge [variant] (BadgeVariant) renamed to [status] (typed DsStatusKey); the value is emitted as a data-status attribute, NOT a factory/status-named CSS class, and the component ships NO built-in colour for any value. Full migration is THREE coupled steps — the rename alone leaves badges uncoloured: (1) rename the input, keeping the value: variant=\"active\" -> status=\"active\", [variant]=\"expr\" -> [status]=\"expr\" (a static variant=\"x\" left on ds-badge is a SILENT failure — Angular ignores the unknown attribute rather than erroring — so grep variant= scoped to ds-badge). (2) Wire colours via the styles/status SCSS API keyed on [data-status] (see status-lifecycle-tokens-removed for the @use/@include snippet). (3) For TS type-safety, augment DsStatusRegistry with your keys so DsStatusKey narrows from open string to your union. NOTE for consumers who coloured badges via their OWN status-named class (class=\"chip {{ status }}\" + ds-badge.chip.completed{...}) instead of [variant]: that keeps working (the --ds-badge-* hooks are unchanged), BUT any value that previously fell through to a FACTORY colour is now uncoloured — move colour off the class onto [data-status] via styles/status. Full guide + before/after: migrations/0.5.1/badge-statuses.md. [count]/[solid]/[withDot]/[max] and the --ds-badge-* hooks are unchanged.",
338
+ "action": "Three coupled steps. (1) Rename the input, keeping the value: `variant=\"active\"` → `status=\"active\"`, `[variant]=\"expr\"` → `[status]=\"expr\"`. (2) Wire the colours through the `styles/status` SCSS API keyed on `[data-status]` — see status-lifecycle-tokens-removed for the snippet. (3) Augment DsStatusRegistry with your keys so DsStatusKey narrows from an open string to your union. Full guide: migrations/0.5.1/badge-statuses.md.",
339
+ "appliesWhen": "`[count]`, `[solid]`, `[withDot]`, `[max]` and every `--ds-badge-*` hook are unchanged. If you coloured badges through your OWN class (`class=\"chip {{ status }}\"`), that keeps working — but any value that used to fall through to a factory colour is now uncoloured.",
340
+ "pitfall": "Step 1 alone leaves every badge UNCOLOURED, because the component ships no built-in colour for any value. And a static `variant=\"x\"` left behind fails silently: Angular ignores an unknown attribute instead of erroring, so the badge renders plain with nothing in the console. Grep `variant=` scoped to ds-badge.",
341
+ "note": "The value is emitted as a `data-status` attribute now rather than a status-named CSS class, and the input is typed DsStatusKey.",
317
342
  "searchHints": [
318
343
  "<ds-badge",
319
344
  "variant=\"",
320
345
  "[variant]="
321
346
  ],
322
- "surface": "template"
347
+ "surface": [
348
+ "template",
349
+ "style",
350
+ "typescript"
351
+ ],
352
+ "verify": "No `variant` remains on the component. The chips render in their status colours, not grey: the `styles/status` partial is included and any custom status is registered through DsStatusRegistry, or the colour resolves to the neutral default and you meant that."
323
353
  },
324
354
  {
325
355
  "id": "status-dot-status-retype",
326
356
  "kind": "behavior",
327
357
  "old": "ds-status-dot",
328
358
  "new": null,
329
- "note": "ds-status-dot [status] keeps its name but is retyped StatusValue -> DsStatusKey and no longer defaults to 'planning'; the value is now emitted as a data-status attribute, not a `.status-dot <value>` CSS class. Any custom CSS targeting .status-dot.active / .planning / .confirmed / .completed / .warning / .error / .secondary must switch to [data-status='...']. Define status colours via the styles/status SCSS API.",
359
+ "action": "Switch any CSS targeting `.status-dot.active`, `.planning`, `.confirmed`, `.completed`, `.warning`, `.error` or `.secondary` to `[data-status='…']`, and define the colours through the `styles/status` SCSS API.",
360
+ "pitfall": "The input name did not change, so a search for `status` finds nothing wrong while the class-based CSS stops matching. It also no longer defaults to `planning` — a dot with no status now has none.",
361
+ "note": "`[status]` is retyped from StatusValue to DsStatusKey and the value reaches the DOM as `data-status`.",
330
362
  "searchHints": [
331
363
  "<ds-status-dot",
332
364
  ".status-dot"
@@ -350,7 +382,8 @@
350
382
  "kind": "removed-api",
351
383
  "old": "BadgeVariant",
352
384
  "new": null,
353
- "note": "The exported types BadgeVariant, BadgeLifecycle, BadgeSemantic (badge) and StatusValue (status-dot) are no longer exported. Type badge/status-dot status with DsStatusKey (or your own registered union via DsStatusRegistry augmentation).",
385
+ "action": "Type badge and status-dot status with DsStatusKey, or with your own union registered through a DsStatusRegistry augmentation.",
386
+ "note": "BadgeVariant, BadgeLifecycle, BadgeSemantic and StatusValue are no longer exported.",
354
387
  "searchHints": [
355
388
  "BadgeVariant",
356
389
  "BadgeLifecycle",
@@ -371,7 +404,10 @@
371
404
  "kind": "removed-api",
372
405
  "old": "--status-planning-bg-color",
373
406
  "new": null,
374
- "note": "The factory lifecycle status theme tokens --status-planning-bg-color / -text-color, --status-confirmed-*, --status-active-*, --status-completed-* are removed. If you set them to theme lifecycle badges/dots, declare your statuses instead via the styles/status SCSS API, which writes the public --ds-badge-* / --ds-status-dot-* tokens keyed on [data-status]. Example: `@use '@ids-group-ltd/ids-design-system/styles/status' as status; @include status.define(('completed': (bg: var(--success), text: var(--text-on-success)), 'active': (bg: var(--info-subtitle), text: var(--info-text))));` — one entry per status value you pass to ds-badge/ds-status-dot [status]; entry shape is (bg required, text?, dot?); or use status.semantic-preset for the info/success/warning/error/neutral set. Pair with the DsStatusRegistry TS augmentation (see badge-variant-to-status-rename) so [status] is type-checked. Full guide: migrations/0.5.1/badge-statuses.md. The dimension token --status-dot-size is NOT removed.",
407
+ "action": "Declare your statuses through the styles/status API instead: `@use '@ids-group-ltd/ids-design-system/styles/status' as status;` then `@include status.define(('completed': (bg: var(--success), text: var(--text-on-success)), 'active': (bg: var(--info-subtitle), text: var(--info-text))));` — one entry per value you pass to `[status]`, shape `(bg required, text?, dot?)`. `status.semantic-preset` covers the info/success/warning/error/neutral set. Pair it with the DsStatusRegistry augmentation. Full guide: migrations/0.5.1/badge-statuses.md.",
408
+ "appliesWhen": "The dimension token `--status-dot-size` is NOT removed and needs nothing.",
409
+ "pitfall": "These tokens were the only colour those badges and dots had. Removing them without defining the replacements leaves the elements rendering with no status colour at all — nothing errors, the colour is simply gone.",
410
+ "note": "The factory lifecycle tokens `--status-planning-*`, `--status-confirmed-*`, `--status-active-*` and `--status-completed-*` are gone; the API writes the public `--ds-badge-*` / `--ds-status-dot-*` hooks keyed on `[data-status]`.",
375
411
  "searchHints": [
376
412
  "--status-planning",
377
413
  "--status-confirmed",
@@ -392,7 +428,10 @@
392
428
  "kind": "behavior",
393
429
  "old": "--secondary-h",
394
430
  "new": null,
395
- "note": "Default secondary/tertiary hues changed: --secondary-h/s/l now default to the --orange palette family (warm orange) and --tertiary-h/s/l to --violet (cool violet), where they previously both defaulted to --primary channels (blue). Consumers who never set --secondary-h/s/l or --tertiary-h/s/l now render orange/violet where they saw blue — VISUAL REVIEW (usually no code change). To keep the old single-hue look, set --secondary-h/s/l and --tertiary-h/s/l back to var(--primary-h/s/l).",
431
+ "action": "Look at anything using the secondary or tertiary roles. To keep the old single-hue look, set `--secondary-h/s/l` and `--tertiary-h/s/l` back to `var(--primary-h/s/l)`.",
432
+ "appliesWhen": "Only if you never set those channels yourself. If you did, your values still win.",
433
+ "pitfall": "Both roles used to fall through to the primary channels, so everything that read them was blue. They are orange and violet now, and because no markup or API moved, the only thing that reports it is a screen.",
434
+ "note": "`--secondary-h/s/l` default to the `--orange` family and `--tertiary-h/s/l` to `--violet`.",
396
435
  "searchHints": [
397
436
  "--secondary-h",
398
437
  "--tertiary-h",
@@ -408,7 +447,9 @@
408
447
  "kind": "removed-api",
409
448
  "old": "--static-white",
410
449
  "new": "white",
411
- "note": "The fixed-value --static-white custom property is removed; replace any var(--static-white) with the literal keyword white (identical value, no visual change). --static-ink is retained.",
450
+ "action": "Replace `var(--static-white)` with the keyword `white`.",
451
+ "appliesWhen": "`--static-ink` is retained and needs nothing.",
452
+ "note": "Identical value, no visual change — the fixed-value custom property earned nothing over the keyword.",
412
453
  "searchHints": [
413
454
  "--static-white",
414
455
  "var(--static-white)"
@@ -426,5 +467,6 @@
426
467
  "Visual/behavioral only, no code change: press-feedback reworked (no button-style press on non-buttons; list/menu rows and color-picker trigger get a flat :active tint; small icon action buttons — close/dismiss/clear/remove x and the ds-tag chip close — get the button press-scale); booleanAttribute coercion on ~54 boolean inputs; ds-button tonal :active now darkens past hover.",
427
468
  "Fixes, no action required: overlay panel --ds-* overrides now reach the portaled pane (ds-autocomplete/ds-multi-select/ds-date-picker/ds-color-picker/ds-popover/ds-time-picker); ds-autocomplete/ds-multi-select panels no longer render transparent; ds-tabs secondary variant now applies; ds-date-picker range mask no longer clips the second date + tighter value-to-icon gap; the ultra-compact density tier now scales avatar/sidenav/badge/status-dot/switch geometry.",
428
469
  "Visual/behavioral only, no code change: ds-date-picker keeps the format mask visible while typing — the unfilled tail of the mask stays on-screen as a muted ghost (e.g. \"12/DD/YYYY\") and the typed value renders in the monospace font for exact glyph alignment."
429
- ]
470
+ ],
471
+ "deleteList": []
430
472
  }
@@ -6,7 +6,10 @@
6
6
  "kind": "code-add",
7
7
  "old": null,
8
8
  "new": "@use '@ids-group-ltd/ids-design-system/styles/breakpoints' as bp;\n@include bp.emit-vars;",
9
- "note": "styles/breakpoints stays side-effect-free on plain @use (map/$bp-*/up()/down() only, no CSS emitted) — the --bp-* runtime custom properties are now emitted only by its emit-vars mixin. Only consumers who followed the 0.4.0 guidance and `@use '@ids-group-ltd/ids-design-system/styles/breakpoints'` A LA CARTE (not via the styles/ds aggregate, which already includes emit-vars once) must additionally `@include bp.emit-vars;` to keep --bp-* defined. Consumers using styles/ds need no action. $bp-* Sass aliases and the up()/down() mixins are unaffected either way.",
9
+ "action": "Add `@include bp.emit-vars;` once, beside your a-la-carte `@use` of `styles/breakpoints`, in exactly one global stylesheet.",
10
+ "appliesWhen": "Only if you took the 0.4.0 advice and imported `styles/breakpoints` a la carte. The `styles/ds` aggregate already includes emit-vars once, so its users need nothing.",
11
+ "pitfall": "Sass still compiles clean, which is what makes this quiet: `$bp-*` and the `up()` / `down()` mixins come from the plain `@use` and keep working, so every media query is fine. What disappears is the runtime mirror — anything reading `var(--bp-md)` from CSS or through getComputedStyle now reads nothing.",
12
+ "note": "The partial is side-effect-free on a plain `@use` now: it carries the map, the `$bp-*` aliases and the mixins, and emits no CSS. The `--bp-*` custom properties come only from `emit-vars`, which is meant to run once per document.",
10
13
  "searchHints": [
11
14
  "styles/breakpoints",
12
15
  "@use '@ids-group-ltd/ids-design-system/styles/breakpoints'"
@@ -32,5 +35,6 @@
32
35
  "ds-date-picker paste is now slot-aware — pasted digits fill segments sequentially from the caret instead of flattening the field or clearing unrelated segments; behavior only, no code change.",
33
36
  "ds-date-picker range values can no longer be corrupted by clearing one segment (slot-based parsing replaced digit-count slicing; a date is parsed/validated only once all its slots are filled) — behavior only, no code change.",
34
37
  "ds-date-picker now exposes its MM/DD/YYYY format hint to screen readers via aria-placeholder after the native placeholder was removed for the overlay rework — a11y only, no code change."
35
- ]
38
+ ],
39
+ "deleteList": []
36
40
  }
@@ -3,7 +3,25 @@
3
3
  "items": [],
4
4
  "informational": [
5
5
  "ds-date-picker's panel now closes when ANY ancestor scroll container scrolls, not only the one 0.6.0 watched. Nothing to change: a panel that used to hang over the page while a nested pane scrolled underneath now dismisses itself.",
6
- "ds-date-picker masked typing works on mobile keyboards. Segment-aware editing was wired to keydown, which soft keyboards (Gboard among them) do not report faithfully; the mobile path now goes through beforeinput. If you shipped a workaround that bypassed the masked field on touch devices, it can go.",
6
+ "ds-date-picker masked typing works on mobile keyboards. Segment-aware editing was wired to keydown, which soft keyboards (Gboard among them) do not report faithfully; the mobile path now goes through beforeinput. If you shipped a workaround that bypassed the masked field on touch devices, it can go. (delete list: date-picker-touch-bypass-workaround)",
7
7
  "ds-date-picker's panel no longer sets aria-modal. The calendar is non-modal - the page stays interactive behind it - so the attribute told screen readers something untrue. No API changed; an assistive-tech test that asserted aria-modal on this panel needs updating."
8
+ ],
9
+ "deleteList": [
10
+ {
11
+ "id": "date-picker-touch-bypass-workaround",
12
+ "surface": [
13
+ "template",
14
+ "typescript"
15
+ ],
16
+ "find": [
17
+ "ds-date-picker",
18
+ "pointer: coarse",
19
+ "ontouchstart",
20
+ "matchMedia",
21
+ "type=\"date\""
22
+ ],
23
+ "why": "A branch that swapped ds-date-picker for a native input, or disabled its masked typing, on touch devices. It existed because segment-aware editing was wired to keydown, which soft keyboards do not report faithfully; the mobile path goes through beforeinput now, so the masked field works there.",
24
+ "replaceWith": "nothing - render ds-date-picker on touch as well"
25
+ }
8
26
  ]
9
27
  }
@@ -6,7 +6,9 @@
6
6
  "kind": "behavior",
7
7
  "old": "ds-bottom-sheet",
8
8
  "new": null,
9
- "note": "ds-bottom-sheet's Escape handler moved from the DOCUMENT to its own panel, matching ds-modal and ds-drawer. Why it changed: with stacked overlays a background sheet was swallowing the Escape meant for whatever sat on top. ACTION, and it is a real one: Escape now has to land on the panel, which the focus trap arranges by auto-capturing focus inside it - so a sheet whose body contains NOTHING FOCUSABLE can no longer be closed with Escape. If you have such a sheet (a purely informational one, say), give it a focusable element: the close button in its header is enough. CHECK: open each sheet, press Escape without clicking anything first.",
9
+ "action": "Open each sheet and press Escape without clicking anything first. If one does not close, give its body something focusable — the close button in its header is enough.",
10
+ "pitfall": "A sheet whose body contains NOTHING focusable can no longer be dismissed with Escape at all: the key has to land on the panel, and the focus trap only gets it there by capturing focus inside. A purely informational sheet is exactly the shape that has nothing to focus, and a keyboard user is then stuck in it.",
11
+ "note": "The Escape handler moved from the document to the panel, matching ds-modal and ds-drawer, because with stacked overlays a background sheet was swallowing the Escape meant for whatever sat on top.",
10
12
  "searchHints": [
11
13
  "ds-bottom-sheet",
12
14
  "bottom-sheet",
@@ -6,7 +6,9 @@
6
6
  "kind": "input-rename",
7
7
  "old": "ds-date-picker[defaultMonth]",
8
8
  "new": "defaultDate",
9
- "note": "Pure rename, behavior unchanged: the input always took a full Date and the calendar opens on its month with grid focus on its exact day (only when the value is empty; never written to the value). [defaultMonth] -> [defaultDate]. No other component has a defaultMonth input.",
9
+ "action": "Rename `[defaultMonth]` to `[defaultDate]` on ds-date-picker.",
10
+ "appliesWhen": "No other component has a defaultMonth input, so the rename is unambiguous.",
11
+ "note": "Behaviour is unchanged: the input always took a full Date, and the calendar still opens on its month with grid focus on its exact day — only while the value is empty, and never written into the value.",
10
12
  "searchHints": [
11
13
  "[defaultMonth]",
12
14
  "defaultMonth"
@@ -18,7 +20,10 @@
18
20
  "kind": "behavior",
19
21
  "old": null,
20
22
  "new": null,
21
- "note": "ds-table row hover tint is now rendered ONLY when rowInteractive is set (clickable rows also gain a pressed :active fill via --ds-table-row-pressed-bg-color). Was: every table tinted rows on hover. No code compiles differently — visual/behavior only. If a passive table must keep the old always-on hover, add consumer CSS: ds-table tbody tr:hover td { background-color: var(--surface-secondary); }. Tables that already set rowInteractive need no action.",
23
+ "action": "None, unless a passive table must keep its hover tint. To keep it: `ds-table tbody tr:hover td { background-color: var(--surface-secondary); }`.",
24
+ "appliesWhen": "Tables that already set `rowInteractive` need nothing — they keep the tint and gain a pressed fill.",
25
+ "pitfall": "Nothing compiles differently, so this only shows on screen. A table that reads as clickable because of the hover tint, without ever having been clickable, quietly loses the affordance it should not have had.",
26
+ "note": "The row hover tint is rendered only when `rowInteractive` is set; clickable rows also gain a pressed `:active` fill through `--ds-table-row-pressed-bg-color`.",
22
27
  "searchHints": [
23
28
  "<ds-table",
24
29
  "rowInteractive"
@@ -36,7 +41,10 @@
36
41
  "kind": "behavior",
37
42
  "old": null,
38
43
  "new": null,
39
- "note": "Only affects a consumer that EXTENDS the DS TableComponent class. Subclassing a DS component is unsupported (design-system.md - Components), but where it happens this release breaks the build: the new column API added ~76 members to TableComponent, so a subclass that already used one of those names no longer compiles — TS4114 requires an 'override' modifier, TS2416 fires where the signature differs. Collisions observed: zebra, columnOrder, orderedColumns, visibleColumns, toggleColumn, onColumnDrop, moveColumn, resetColumns, columnFilters, exportCsv, onResizeMove, onResizeEnd. Resolution per member: where the base member means the same thing, keep the name and add `override` with a base-compatible signature (zebra must adopt the base's booleanAttribute transform); otherwise RENAME the subclass's own member — the private/protected ones are internal to the component and its own template, so renaming is behaviour-preserving, but check the new name against the base's member list so it does not collide again. Build the consumer right after the bump: the compiler enumerates every collision. A consumer that only uses the <ds-table> element needs no action.",
44
+ "action": "Build the consumer immediately after the bump — the compiler enumerates every collision. Per member: where the base means the same thing, keep the name and add `override` with a base-compatible signature; otherwise rename your own member. Base members it collides on: zebra, columnOrder, orderedColumns, visibleColumns, toggleColumn, onColumnDrop, moveColumn, resetColumns, columnFilters, exportCsv, onResizeMove, onResizeEnd.",
45
+ "appliesWhen": "Only a consumer that EXTENDS TableComponent. Subclassing a DS component is unsupported (design-system.md § Components); anyone using the `<ds-table>` element is unaffected.",
46
+ "pitfall": "Two ways to fix it wrongly. Adding `override` to `zebra` without adopting the base booleanAttribute transform changes what the input accepts. And renaming your member to something else can collide again — check the new name against the base member list, because the private and protected ones are internal and give no warning.",
47
+ "note": "The new column API added about 76 members to TableComponent, so a subclass that already used one of those names stops compiling: TS4114 wants an `override` modifier, TS2416 fires where the signature differs.",
40
48
  "searchHints": [
41
49
  "extends TableComponent",
42
50
  "extends "
@@ -73,5 +81,6 @@
73
81
  "New ds-app-shell — a slotted fixed-frame application shell ([sidenav]/[topbar]/default content slots) that pins to the viewport (100dvh, overflow: hidden) so only the content <main> scrolls (scrollbar-gutter: stable + automatic native-scrollbar-width padding compensation via the new --ds-scrollbar-width root variable); topbarSpan input ('content' default full-height rail | 'full' full-width topbar) switches the geometry; scroll-to-top on router navigation via the new exported ShellScrollService (also injectable from routed pages for manual scrollToTop()). Tokens: --ds-app-shell-pad-x/-pad-y/-content-max-width/-height — additive, no code change.",
74
82
  "New ds-sidenav-footer — a rail footer brick: Search row with a live grouped-results popover, Alerts row with an unread dot + feed popover, Collapse row, and a user card with an account menu; inputs userName/userRole/alerts/collapsed/searchProvider/alertItems/profileRoute, outputs collapseToggled/alertsOpened/signOutSelected; new exported types SidenavSearchProvider/SidenavSearchResult/SidenavAlertItem. Tokens: --ds-sidenav-footer-popover-width/-popover-max-width/-popover-max-height/-head-tracking/-dot-size — additive, no code change.",
75
83
  "ds-sidenav gains an optional logoLetter input (sets the brand-tile glyph when it differs from the brand's first letter) and a [dsBrandName] projection slot (exported marker directive BrandNameDirective) that renders custom wordmark markup inside .brand-name in place of the plain brand text — both optional, omitting them renders exactly as before, additive, no code change."
76
- ]
84
+ ],
85
+ "deleteList": []
77
86
  }