@ids-group-ltd/ids-design-system 0.10.2 → 0.11.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.
@@ -6,7 +6,8 @@
6
6
  "kind": "selector-rename",
7
7
  "old": "ds-combobox",
8
8
  "new": "ds-autocomplete",
9
- "note": "Component renamed (clearer industry name); behavior unchanged.",
9
+ "action": "Replace the element selector `ds-combobox` with `ds-autocomplete`.",
10
+ "note": "A rename to the industry word for the control. Behaviour is unchanged.",
10
11
  "searchHints": [
11
12
  "<ds-combobox",
12
13
  "ds-combobox"
@@ -18,7 +19,7 @@
18
19
  "kind": "type-rename",
19
20
  "old": "ComboboxComponent",
20
21
  "new": "AutocompleteComponent",
21
- "note": "TS import/reference rename only.",
22
+ "action": "Replace `ComboboxComponent` with `AutocompleteComponent` in imports and references.",
22
23
  "searchHints": [
23
24
  "ComboboxComponent"
24
25
  ],
@@ -29,7 +30,8 @@
29
30
  "kind": "type-rename",
30
31
  "old": "ComboboxOption",
31
32
  "new": "AutocompleteOption",
32
- "note": "TS type rename. Beware token boundaries: ComboboxOptionGroup contains ComboboxOption — rename the longer identifier first (its own item).",
33
+ "action": "Replace `ComboboxOption` with `AutocompleteOption`, matching whole identifiers.",
34
+ "pitfall": "`ComboboxOptionGroup` CONTAINS `ComboboxOption`. A substring replace run on the short name first corrupts the long one into a name that exists nowhere. Apply the group item first, or match whole identifiers.",
33
35
  "searchHints": [
34
36
  "ComboboxOption"
35
37
  ],
@@ -40,7 +42,7 @@
40
42
  "kind": "type-rename",
41
43
  "old": "ComboboxOptionGroup",
42
44
  "new": "AutocompleteOptionGroup",
43
- "note": "TS type rename.",
45
+ "action": "Replace `ComboboxOptionGroup` with `AutocompleteOptionGroup`. Apply this before the shorter `ComboboxOption`.",
44
46
  "searchHints": [
45
47
  "ComboboxOptionGroup"
46
48
  ],
@@ -51,7 +53,7 @@
51
53
  "kind": "type-rename",
52
54
  "old": "ComboboxSize",
53
55
  "new": "AutocompleteSize",
54
- "note": "TS type rename.",
56
+ "action": "Replace `ComboboxSize` with `AutocompleteSize`.",
55
57
  "searchHints": [
56
58
  "ComboboxSize"
57
59
  ],
@@ -62,7 +64,7 @@
62
64
  "kind": "type-rename",
63
65
  "old": "ComboboxWidth",
64
66
  "new": "AutocompleteWidth",
65
- "note": "TS type rename.",
67
+ "action": "Replace `ComboboxWidth` with `AutocompleteWidth`.",
66
68
  "searchHints": [
67
69
  "ComboboxWidth"
68
70
  ],
@@ -73,7 +75,7 @@
73
75
  "kind": "token-rename",
74
76
  "old": "--ds-combobox-",
75
77
  "new": "--ds-autocomplete-",
76
- "note": "Prefix rename covering --ds-combobox-focus-shadow / -maxw / -input-minw; replace within each full suffixed name.",
78
+ "action": "Replace the prefix `--ds-combobox-` with `--ds-autocomplete-` inside each full token name: `-focus-shadow`, `-maxw`, `-input-minw`.",
77
79
  "searchHints": [
78
80
  "--ds-combobox-"
79
81
  ],
@@ -84,7 +86,9 @@
84
86
  "kind": "behavior",
85
87
  "old": "#combobox",
86
88
  "new": null,
87
- "note": "Docs-site anchor renamed #combobox -> #autocomplete; update any hardcoded documentation links in consumer code/README.",
89
+ "action": "Update any hardcoded documentation link pointing at `#combobox` to `#autocomplete`.",
90
+ "appliesWhen": "Only where a link to the docs site is written into your own code or README.",
91
+ "note": "The docs page moved with the component rename, so the fragment that used to address it no longer resolves and the link lands at the top of the page.",
88
92
  "searchHints": [
89
93
  "#combobox"
90
94
  ],
@@ -102,7 +106,8 @@
102
106
  "kind": "selector-rename",
103
107
  "old": "ds-dropdown",
104
108
  "new": "ds-select",
105
- "note": "ds-dropdown removed; ds-select is the canonical select-only picker (CVA, invalid+hint, required/optional, per-option icons, readOnly). After the selector rename also apply dropdown-error-input-rename and dropdown-option-groups-fold (separate items).",
109
+ "action": "Replace `ds-dropdown` with `ds-select`, then apply `dropdown-error-input-rename` and `dropdown-option-groups-fold` to the same elements.",
110
+ "note": "ds-dropdown is gone; ds-select is the one select-only picker, and it carries the CVA, invalid and hint, required and optional, per-option icons and readOnly.",
106
111
  "searchHints": [
107
112
  "<ds-dropdown",
108
113
  "ds-dropdown"
@@ -114,7 +119,7 @@
114
119
  "kind": "input-rename",
115
120
  "old": "ds-dropdown[error]",
116
121
  "new": "invalid",
117
- "note": "On elements migrated from ds-dropdown to ds-select: [error] -> [invalid] (and static error=\"...\" -> invalid=\"...\").",
122
+ "action": "On elements you moved from `ds-dropdown` to `ds-select`, rename `[error]` to `[invalid]` and `error=\"…\"` to `invalid=\"…\"`.",
118
123
  "searchHints": [
119
124
  "[error]=",
120
125
  "error=\""
@@ -126,7 +131,9 @@
126
131
  "kind": "behavior",
127
132
  "old": "ds-dropdown[optionGroups]",
128
133
  "new": null,
129
- "note": "[optionGroups]=\"groups\" is gone on ds-select — pass groups inline in [options]: SelectItem = SelectOption | SelectOptionGroup, so merge the flat options and the groups into one [options] array (order = desired render order).",
134
+ "action": "Merge the flat options and the groups into one `[options]` array. `SelectItem` is `SelectOption | SelectOptionGroup`, so both shapes sit in the same list.",
135
+ "pitfall": "The array order IS the render order now. Two separate inputs used to be rendered in a fixed sequence, so concatenating them the other way round silently reshuffles the list and nothing warns.",
136
+ "note": "`[optionGroups]` no longer exists on ds-select.",
130
137
  "searchHints": [
131
138
  "[optionGroups]="
132
139
  ],
@@ -145,7 +152,7 @@
145
152
  "kind": "type-rename",
146
153
  "old": "DropdownComponent",
147
154
  "new": "SelectComponent",
148
- "note": "TS import/reference rename.",
155
+ "action": "Replace `DropdownComponent` with `SelectComponent` in imports and references.",
149
156
  "searchHints": [
150
157
  "DropdownComponent"
151
158
  ],
@@ -156,7 +163,8 @@
156
163
  "kind": "type-rename",
157
164
  "old": "DropdownOption",
158
165
  "new": "SelectOption",
159
- "note": "TS type rename. Token boundaries: DropdownOptionGroup contains DropdownOption — rename the longer identifier first.",
166
+ "action": "Replace `DropdownOption` with `SelectOption`, matching whole identifiers.",
167
+ "pitfall": "`DropdownOptionGroup` contains `DropdownOption`. Apply the group item first, or match whole identifiers — a substring replace corrupts the longer name.",
160
168
  "searchHints": [
161
169
  "DropdownOption"
162
170
  ],
@@ -167,7 +175,7 @@
167
175
  "kind": "type-rename",
168
176
  "old": "DropdownOptionGroup",
169
177
  "new": "SelectOptionGroup",
170
- "note": "TS type rename.",
178
+ "action": "Replace `DropdownOptionGroup` with `SelectOptionGroup`. Apply this before the shorter `DropdownOption`.",
171
179
  "searchHints": [
172
180
  "DropdownOptionGroup"
173
181
  ],
@@ -178,7 +186,7 @@
178
186
  "kind": "type-rename",
179
187
  "old": "DropdownSize",
180
188
  "new": "SelectSize",
181
- "note": "TS type rename.",
189
+ "action": "Replace `DropdownSize` with `SelectSize`.",
182
190
  "searchHints": [
183
191
  "DropdownSize"
184
192
  ],
@@ -189,7 +197,8 @@
189
197
  "kind": "token-rename",
190
198
  "old": "--ds-datepicker-",
191
199
  "new": "--ds-date-picker-",
192
- "note": "Prefix normalized to match the selector (~14 tokens). Names only — CSS property and defaults byte-identical. Replace within each full suffixed name.",
200
+ "action": "Replace the prefix `--ds-datepicker-` with `--ds-date-picker-` inside each full token name — about fourteen tokens.",
201
+ "note": "Names only: the prefix matches the selector now, and every value and CSS property is byte-identical.",
193
202
  "searchHints": [
194
203
  "--ds-datepicker-"
195
204
  ],
@@ -200,7 +209,8 @@
200
209
  "kind": "token-rename",
201
210
  "old": "--ds-statusdot-",
202
211
  "new": "--ds-status-dot-",
203
- "note": "Prefix normalized (color, size). Names only.",
212
+ "action": "Replace the prefix `--ds-statusdot-` with `--ds-status-dot-` inside each full token name — `-color` and `-size`.",
213
+ "note": "Names only: the prefix matches the selector now, and every value and CSS property is byte-identical.",
204
214
  "searchHints": [
205
215
  "--ds-statusdot-"
206
216
  ],
@@ -211,7 +221,8 @@
211
221
  "kind": "token-rename",
212
222
  "old": "--ds-pagehdr-",
213
223
  "new": "--ds-page-header-",
214
- "note": "Prefix normalized (~10 tokens: eyebrow/title/subtitle/meta/crumb colors, meta-icon-color, divider, title-fs, title-gap). Names only.",
224
+ "action": "Replace the prefix `--ds-pagehdr-` with `--ds-page-header-` inside each full token name — the page-header hooks.",
225
+ "note": "Names only: the prefix matches the selector now, and every value and CSS property is byte-identical.",
215
226
  "searchHints": [
216
227
  "--ds-pagehdr-"
217
228
  ],
@@ -222,7 +233,8 @@
222
233
  "kind": "token-rename",
223
234
  "old": "--ds-avatargroup-",
224
235
  "new": "--ds-avatar-group-",
225
- "note": "Prefix normalized (overlap, ring, overflow-bg-color, overflow-label-color). Names only.",
236
+ "action": "Replace the prefix `--ds-avatargroup-` with `--ds-avatar-group-` inside each full token name — `-overlap`, `-ring`, `-overflow-bg-color` and `-overflow-label-color`.",
237
+ "note": "Names only: the prefix matches the selector now, and every value and CSS property is byte-identical.",
226
238
  "searchHints": [
227
239
  "--ds-avatargroup-"
228
240
  ],
@@ -233,7 +245,10 @@
233
245
  "kind": "class-rename",
234
246
  "old": "ds-search .input",
235
247
  "new": ".search-input",
236
- "note": "ds-search's inner input class renamed (over-generic .input let consumer global styles leak in). Only consumer STYLING that targeted the undocumented internal class is affected — scope strictly to selectors under ds-search.",
248
+ "action": "Rename `.input` to `.search-input` in selectors scoped under `ds-search`.",
249
+ "appliesWhen": "Only if you styled the undocumented inner class. Nothing in the public API moved.",
250
+ "pitfall": "Scope the replace to selectors under ds-search. `.input` is generic enough that a repo-wide rename hits your own unrelated rules — the same leak this rename exists to stop.",
251
+ "note": "The inner input class was over-generic, so a consumer global `.input` rule leaked into the component.",
237
252
  "searchHints": [
238
253
  "ds-search"
239
254
  ],
@@ -244,7 +259,9 @@
244
259
  "kind": "behavior",
245
260
  "old": "ds-date-picker",
246
261
  "new": null,
247
- "note": "Trigger is now an editable masked text input by default (allowInput defaults true) with a trailing calendar icon, and the field sizes to CONTENT width (was full-width). Pass [allowInput]=\"false\" for the old click-only field; set a width on the host to stretch. Usually no code change — flag for visual review (eyeball).",
262
+ "action": "Look at every date picker. For the old click-only field pass `[allowInput]=\"false\"`; to keep it full-width, set a width on the host.",
263
+ "pitfall": "Two defaults moved at once and neither breaks a build: the field went from full-width to content-width, so a picker that used to fill its column now sits narrow inside it and the layout tuned around it has a hole.",
264
+ "note": "The trigger is an editable masked text input by default (allowInput defaults to true) with a trailing calendar icon, and it sizes to its content.",
248
265
  "searchHints": [
249
266
  "<ds-date-picker"
250
267
  ],
@@ -264,7 +281,9 @@
264
281
  "kind": "behavior",
265
282
  "old": "ds-date-picker",
266
283
  "new": null,
267
- "note": "The selected-date/value display now defaults to `en-US` formatting via the new `locale` input (effective locale = [locale] ?? provideDsConfig datePicker.locale ?? 'en-US'), replacing the previous ambient browser `toLocaleDateString()`. A consumer whose users run a non-US browser locale (en-GB, de, fr, ...) will see a silently DIFFERENT date format with no markup change. To restore OS/ambient-driven display, set `[locale]` per instance or `provideDsConfig({ datePicker: { locale } })` app-wide.",
284
+ "action": "If your readers are not en-US, set the locale: `[locale]` per instance, or `provideDsConfig({ datePicker: { locale } })` app-wide.",
285
+ "pitfall": "The old display followed the ambient browser locale, so on your own machine nothing need look different while an en-GB or de reader sees a silently reformatted date. No markup changes and nothing logs.",
286
+ "note": "The value display resolves `[locale] ?? provideDsConfig datePicker.locale ?? 'en-US'` instead of calling toLocaleDateString() with the browser default.",
268
287
  "searchHints": [
269
288
  "<ds-date-picker",
270
289
  "toLocaleDateString"
@@ -286,7 +305,8 @@
286
305
  "kind": "behavior",
287
306
  "old": "ds-search",
288
307
  "new": null,
289
- "note": "Default max-width changed 320px -> none (ds-search now stretches like the rest of the field family). If the 320px cap was relied on, set --ds-search-maxw: 320px on the host/theme. Usually visual-review only.",
308
+ "action": "To keep the old cap, set `--ds-search-maxw: 320px` on the host or in your theme.",
309
+ "note": "The default max-width went from 320px to none, so ds-search stretches like the rest of the field family.",
290
310
  "searchHints": [
291
311
  "<ds-search"
292
312
  ],
@@ -299,7 +319,10 @@
299
319
  "kind": "behavior",
300
320
  "old": "ds-card[elevation=interactive]",
301
321
  "new": null,
302
- "note": "ds-card with the pre-existing `elevation=\"interactive\"` value is now natively keyboard-activatable (Enter/Space trigger the click, with role=\"button\" + tabindex) — new runtime behavior on existing markup. If a consumer hand-rolled a keyboard workaround (a custom (keydown.enter)/(keydown.space) that also fires the action), it now DOUBLE-fires with the native activation — remove the workaround. Cards without elevation=\"interactive\", and consumers who never faked keyboard activation, need no action.",
322
+ "action": "If you hand-rolled keyboard activation on an interactive card — a `(keydown.enter)` or `(keydown.space)` that fires the same action — delete it.",
323
+ "appliesWhen": "Only cards carrying `elevation=\"interactive\"`. Others are untouched, and so is anyone who never faked the keyboard path.",
324
+ "pitfall": "Leaving the workaround makes the action fire TWICE on one key press, because the native activation runs beside it. A double submit or a double navigation is the symptom, and it shows only on the keyboard — a mouse test passes.",
325
+ "note": "`elevation=\"interactive\"` is natively keyboard-activatable now: Enter and Space trigger the click, with role=\"button\" and a tabindex.",
303
326
  "searchHints": [
304
327
  "elevation=\"interactive\"",
305
328
  "elevation=interactive"
@@ -321,5 +344,6 @@
321
344
  "Selection controls gain size + required; standalone ds-radio gains invalid/hint; input/textarea maxLength counter; date-picker minDate/maxDate/disabledDate/presets + locale/dateFormat/firstDayOfWeek/defaultMonth manual masked entry; select clearable/icons/readOnly; autocomplete optionGroups/allowCreate/width=content; table expandable rows; modal closeOnBackdrop/persistent/xl/fullscreen; drawer placement/sm; bottom-sheet snapPoints; toast loading/promise/maxVisible; menu dividers/submenus; popover arrow/placement; tabs lazy/scrollable/closable/vertical; accordion single-open/item disabled; stepper clickable/errorSteps/vertical; sidenav collapsed tooltip; badge count/max; avatar status/fallbackIcon — all additive.",
322
345
  "Public --ds-* customization token sweep across ~44 components (~160-180 new names) — purely additive resolvers, zero visual change when unset.",
323
346
  "Visual-only: rounded press feedback (+ --ds-press-brightness/--ds-press-scale tuning tokens) and native tap-highlight suppression; accessibility hardening across overlays/pickers/fields/cards (dialog semantics, Tab close, role=alert re-announce, labels)."
324
- ]
347
+ ],
348
+ "deleteList": []
325
349
  }
@@ -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 `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."
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
  }