@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
@@ -0,0 +1,216 @@
1
+ {
2
+ "version": "0.11.0",
3
+ "items": [
4
+ {
5
+ "id": "exported-class-members-grew",
6
+ "kind": "behavior",
7
+ "old": "class MyTable extends TableComponent, class MyButton extends ButtonComponent (or any exported DS component you subclass)",
8
+ "new": null,
9
+ "action": "Only if you extend one of these and already declare one of the GAINED names: rename yours, or add `override` if you meant to replace ours. Build after upgrading — the compiler enumerates every collision.",
10
+ "appliesWhen": "Subclassing a DS component is unsupported, but consumers do it. Template users of the `<ds-…>` elements need nothing.",
11
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does. Six members — `hint`, `error`, `warning`, `messageIcon`, `reserveMessage` and `reserveMessageResolved` — moved one level up between two internal base classes, so a member-by-member diff can report them as lost and regained. They still reach your subclass with the same names, types and defaults, and an existing `override` still works because it accepts a member from any ancestor. Nothing to do for those; only the GAINED names below can collide.",
12
+ "note": "Compared against 0.10.3. Gained: TableComponent `cellLink`; ButtonComponent `disabledReason`, `ariaDescribedBy`, `softDisabled`, `message`, `fieldMessage`, `hasMessageRow`, `describedBy`, `hintId`, `reasonId`, `uid`; IconButtonComponent `ariaDescribedBy`; SidenavComponent `brandRoute`, `brandLinkLabel` and the protected `brandAriaLabel`; CheckboxComponent and RadioGroupComponent each the protected `controlState`. TS4114 asks for an `override` modifier, TS2415 fires where the signature differs.",
13
+ "surface": "typescript",
14
+ "verify": "Build your app: no TS4114 or TS2415 is raised against a class that extends a DS component.",
15
+ "searchHints": [
16
+ "extends TableComponent",
17
+ "extends ButtonComponent",
18
+ "extends IconButtonComponent",
19
+ "cellLink",
20
+ "disabledReason",
21
+ "ariaDescribedBy",
22
+ "softDisabled",
23
+ "hasMessageRow",
24
+ "TS4114",
25
+ "TS2415",
26
+ "extends SidenavComponent",
27
+ "brandRoute",
28
+ "brandLinkLabel",
29
+ "brandAriaLabel",
30
+ "controlState",
31
+ "extends DsFieldBase",
32
+ "extends DsMessageBase"
33
+ ],
34
+ "detect": [
35
+ "extends TableComponent",
36
+ "extends ButtonComponent",
37
+ "extends IconButtonComponent",
38
+ "cellLink",
39
+ "disabledReason",
40
+ "ariaDescribedBy",
41
+ "softDisabled",
42
+ "hasMessageRow",
43
+ "TS4114",
44
+ "TS2415",
45
+ "extends SidenavComponent",
46
+ "brandRoute",
47
+ "brandLinkLabel",
48
+ "brandAriaLabel",
49
+ "controlState"
50
+ ]
51
+ },
52
+ {
53
+ "id": "menu-divider-now-flush",
54
+ "kind": "behavior",
55
+ "old": "ds-menu-divider",
56
+ "new": null,
57
+ "surface": "style",
58
+ "note": "A divider is a boundary, not a row, so it no longer takes space of its own: it cancels ds-menu's row gap and the items sit flush against the line. Measured 0px above and 0px below, where it was one row gap (2px at the default --ds-menu-gap) on each side. Its own padding already defaulted to 0 in 0.8.0; this removes the gap that was landing on top of it. The --ds-menu-divider-spacing token is unchanged and still gives the boundary air.",
59
+ "action": "Nothing unless you set --ds-menu-divider-spacing. If you do, your boundary now measures your value alone instead of your value plus the row gap, so add one --ds-menu-gap back into it to keep the previous measurement.",
60
+ "appliesWhen": "Only menus that use ds-menu-divider.",
61
+ "pitfall": "0.8.0's restore recipe (`ds-menu { --ds-menu-divider-spacing: var(--space-1) }`) counts as setting it, so a menu that followed that advice tightens without anyone editing it.",
62
+ "verify": "Open a menu with a divider: the items touch the line. If you set the spacing token, the air either side equals your value exactly.",
63
+ "searchHints": [
64
+ "ds-menu-divider",
65
+ "--ds-menu-divider-spacing",
66
+ "--ds-menu-gap",
67
+ "menu-divider"
68
+ ],
69
+ "detect": [
70
+ "ds-menu-divider",
71
+ "--ds-menu-divider-spacing"
72
+ ]
73
+ },
74
+ {
75
+ "id": "published-manifests-corrected",
76
+ "kind": "behavior",
77
+ "old": "A repo whose last @ids-group-ltd/ids-design-system upgrade ran before this release and crossed 0.2.0, 0.5.1, 0.7.1, 0.8.0, 0.9.0 or 0.10.0",
78
+ "new": null,
79
+ "action": "Re-run these items, now corrected in migrations/<version>.json: 0.2.0#surface-subtle-token-rename, 0.5.1#progress-variant-remap, 0.5.1#badge-variant-to-status-rename, 0.7.1#surface-motion-partial-a-la-carte, 0.7.1#modal-title-flex-moved-to-heading, 0.8.0#table-client-sort-replaced-by-sort-mode, 0.9.0#input-signal-types-widened-by-transforms, 0.10.0#input-floating-removed, 0.10.0#modal-confirm-error-tone-paints-a-badge. Nothing else in those files changed meaning.",
80
+ "appliesWhen": "Only for a repo that already stepped through one of those six versions. A first-time consumer, or one whose upgrade runs from here on, reads the corrected files and needs none of this. The defects are independent - crossing 0.7.1 says nothing about 0.9.0.",
81
+ "pitfall": "Two of these UNDO work rather than adding it. 0.7.1 filed the modal `.title` as a rename to `.heading`; no rename ever happened, so a repo that renamed it on our word must put it back - `.title` still paints the heading text. And 0.7.1 handed out bare `styles/…` @use specifiers that resolve only inside this library's own source tree: the line looks right and fails at build from an app. The 0.8.0 one is the silent case - an unset sortMode was documented as resolving to server when it resolves to client, so a server-paged table passes every check while sorting only the rows already on screen.",
82
+ "note": "Each listed item was corrected against the code of its own release: three changes that had no item, two wrong instructions, one verify that certified a bug, and three items whose surface named too few file types.",
83
+ "surface": [
84
+ "style",
85
+ "template",
86
+ "typescript"
87
+ ],
88
+ "verify": "No `--surface-subtle` remains in any stylesheet. No bare `@use 'styles/…'` of a design-system partial remains - each is package-qualified. Every ds-table that binds [total] declares sortMode=\"server\" explicitly. No `variant` remains on ds-badge or ds-progress in any file type. No stylesheet sets --field-h-floating, --field-floating-label-fs, --field-floating-label-lh, --field-floating-label-top or --field-floating-pad-t. The app builds with no TS2322 naming InputSignal and no TS2416 on a class extending a DS field.",
89
+ "searchHints": [
90
+ "--surface-subtle",
91
+ "@use 'styles/surface-motion'",
92
+ "@use 'styles/overlay-motion'",
93
+ ".heading",
94
+ "sortMode",
95
+ "[total]",
96
+ "variant",
97
+ "--field-h-floating",
98
+ "--field-floating-label-fs",
99
+ "--field-floating-pad-t",
100
+ "InputSignal<",
101
+ "ds-badge",
102
+ "ds-progress",
103
+ "ds-modal-card",
104
+ "floating"
105
+ ],
106
+ "detect": [
107
+ "--surface-subtle",
108
+ "@use 'styles/surface-motion'",
109
+ "@use 'styles/overlay-motion'",
110
+ "--field-h-floating",
111
+ "--field-floating-label-fs",
112
+ "--field-floating-label-lh",
113
+ "--field-floating-label-top",
114
+ "--field-floating-pad-t",
115
+ "InputSignal<",
116
+ "ds-modal-card ::ng-deep .heading"
117
+ ]
118
+ },
119
+ {
120
+ "id": "sidenav-item-without-destination-is-a-button",
121
+ "kind": "behavior",
122
+ "old": "ds-sidenav-item",
123
+ "new": null,
124
+ "surface": "template",
125
+ "note": "A ds-sidenav-item with neither routerLink nor href used to render <a href=\"#\">, which navigates: it rewrites the URL and discards the scroll position on click. It renders <button type=\"button\"> now. Styling is unchanged - the rules are class-based and the button's UA chrome is reset - and both anchor variants behave exactly as before.",
126
+ "action": "Nothing for an item that already sets href or routerLink. An item you INTENDED as a link needs one of those; an empty href no longer becomes \"#\". If any CSS or test selects the item by tag, widen it to the class: `.item` covers all three variants.",
127
+ "appliesWhen": "Only items with no href and no routerLink.",
128
+ "pitfall": "A querySelector('ds-sidenav-item a') or an `a` type selector silently matches nothing for those items now.",
129
+ "verify": "Click a destination-less item: the URL and the scroll position stay put, and `activate` still fires.",
130
+ "searchHints": [
131
+ "ds-sidenav-item",
132
+ "href=\"#\"",
133
+ "sidenav-item a",
134
+ "activate"
135
+ ],
136
+ "detect": [
137
+ "ds-sidenav-item",
138
+ "sidenav-item a"
139
+ ]
140
+ }
141
+ ],
142
+ "informational": [
143
+ "`--ds-field-message-icon-offset` and `--ds-time-picker-focus-shadow` are public, overridable, and listed in the token reference - the supported way to retune either. Nothing changed in the components - if you hand-rolled around either because it looked unsupported, the override is supported and is the way to do it. They belong with the twelve named under 0.10.3.",
144
+ "If you applied 0.10.2 before its manifest was completed, two of its notes were reachable only from the CHANGELOG; this is one of them. components.md, the digest this package carries for your own agent, had named --primary, --text-on-primary and --secondary as the active ds-sidenav-item defaults - the wash replaced them, so an override written against those three does not do what it looks like.",
145
+ "The second note 0.10.2 kept only in its CHANGELOG: `data-focus=\"inset\"` (shipped in that release) draws the focus ring INSIDE the border box, for a subtree under an overflow:hidden ancestor that would otherwise clip it away entirely. It is the only focus style not pinned to :root - set it on the clipping element.",
146
+ "ds-table columns take a new optional `link: (row) => string | readonly unknown[] | null`. Nothing changes on a column that does not set it; see the exported-class-members-grew item if you SUBCLASS TableComponent. Where you compensated for an invisible row click by repeating the destination as a 'View Details' item in the row overflow menu, that item can go: give the name column `link` instead and the destination becomes a real <a> - tabbable as a link, Ctrl/Cmd-clickable, and announced as a link rather than as a table row. If you also set `rowInteractive`, note the pair costs two tab stops per row; the link alone is usually the better trade on a long list. (delete list: row-menu-view-details-duplicate)",
147
+ "ds-card gains --ds-card-overflow, default visible. Opt-in on purpose: clipping a card also cuts the focus ring off any child at its edge, so where a clipped card holds focusable content pair it with data-focus=\"inset\".",
148
+ "ds-button gains --ds-button-shadow and --ds-button-shadow-hover, both default none. Purely additive; -shadow-hover falls back to -shadow, and the focus/pressed hooks still win in their own states.",
149
+ "ds-button gains disabledReason, hint, warning, error, messageIcon, reserveMessage and ariaDescribedBy; ds-icon-button gains ariaDescribedBy. All additive - a button that sets none of them is byte-identical in behaviour and layout. Two things worth knowing before you use them. (1) disabledReason CHANGES HOW THE BUTTON IS DISABLED: with a reason set the button carries aria-disabled=\"true\" instead of the native disabled attribute, so it stays focusable and the reason is announced as its accessible description; the click is swallowed in the handler, so (pressed) still never fires. If you have CSS keyed on `ds-button button[disabled]` or `:disabled`, add `[aria-disabled=\"true\"]` - the library's own disabled paint already covers both. (2) hint/warning/error are for the OTHER kind of refusal: a temporary one the user lifts by filling the form in. Do not disable the button for those - leave it live, judge validity in the submit handler, and let the message line explain. A message-bearing button becomes a column, and since the host shrinks to fit, a message longer than the label widens the pair, button included. (delete list: button-disabled-reason-tooltip)",
150
+ "Every item in every published manifest now carries `action` (the imperative alone, the only field to execute), `appliesWhen` (the boundary, including what is NOT affected) and `pitfall` (the way to apply it correctly and still break the app); `note` keeps the reasoning. If you read these files with your own tooling, read `action` first and `pitfall` before reporting an item done. Nothing was removed - every field that was there is still there with the same name and meaning.",
151
+ "ds-w3w renders `///word.word.word` flush now. It previously showed a space after the `///` prefix (7.8px wider than the format allows, measured), which also disagreed with its own aria-label. Purely a rendering fix - no API change and nothing to edit. Worth a look only if you compensated for the space: a negative margin or a letter-spacing tweak aimed at ds-w3w's mark, or a hand-built pill you wrote because the DS one looked wrong, would now over-correct.",
152
+ "ds-banner now sets `text-align: start` on its own box instead of inheriting. Nothing to do unless you were centring a banner by centring its container - that no longer reaches the banner, and the fix is to say so rather than to work around it. The reported symptom (a centred title over a start-aligned body) does not come from the DS: measured across every banner and both layouts, title and body both compute `start`, and a centred ancestor moves BOTH - it cannot split them. If you still see the split, something on your side targets `.title` or `.body` directly; those are generic class names and a global rule reaches them.",
153
+ "ds-sidenav-footer's account menu uses ds-menu-divider now instead of a hand-rolled div, so --ds-menu-divider-color and --ds-menu-divider-spacing finally reach it. Its line also moves CLOSER - it sat 6px from its neighbours and is flush now, along with every other divider; see the menu-divider-now-flush item for what that means if you set the spacing token.",
154
+ "A compact ds-banner with a title longer than its container used to overflow that container and cut the title mid-word with no ellipsis; it now ellipsises and the banner shrinks to fit. Nothing to edit. Worth a look only if you compensated for it - a width, a min-width or a font-size override on a compact banner, or a title you shortened to stop it blowing out a narrow column, can go back to the wording you wanted.",
155
+ "ds-table's pagination footer is now inset like the cells (horizontally by --ds-table-cell-pad-x, and the same at the bottom as the top). It previously had padding-top only, so the summary line sat 16px left of the column text and on the container's border. Nothing to edit - and if you carried a TODO(ds-table-footer-padding) or a local rule padding .pagination-footer, it can go. A local rule will now DOUBLE the inset, so check for one. (delete list: table-footer-padding-workaround)",
156
+ "ds-banner's projected body takes --font-size-s now, overridable via the new --ds-banner-body-font-size, instead of inheriting the page size - a 16px context used to render the body larger than the banner's own 14px title. The title/body gap also moved onto the body, so it appears only when a body exists: a compact banner with BOTH a title and a body no longer runs them together, and a title-only banner gains no trailing space. If you set a font-size on a banner's content from outside to compensate, drop it or move it to the token.",
157
+ "ds-sidenav gains brandRoute and brandLinkLabel: set brandRoute and the brand row becomes a link (typically to home), announced as \"<brand>, home\" unless brandLinkLabel says otherwise. Unset, the row is the plain block it always was, so nothing changes without an explicit opt-in. Router targets only, and RouterLink is instantiated only once the input is set. If you hand-rolled a link around the brand slot, this replaces it.",
158
+ "ds-checkbox and ds-radio-group paint a validation state on the control now: the checkbox reddens its border (border only - a fill at 16px reads as checked), the radio group reddens its label (not the rings - an unanswered group is not five wrong radios). Both also handle warning. Purely additive, and only visible where you already bind error/errors/invalid. ds-radio, ds-switch and ds-slider deliberately do NOT paint: a lone radio's choice belongs to its group, a switch applies on flip rather than on submit, and a slider always holds an in-range value. If you hand-rolled a red outline on a checkbox or a red group label, drop it - it will now double up."
159
+ ],
160
+ "deleteList": [
161
+ {
162
+ "id": "card-overflow-ng-deep-workaround",
163
+ "surface": "style",
164
+ "find": [
165
+ "ds-card .card",
166
+ "overflow: hidden",
167
+ "::ng-deep"
168
+ ],
169
+ "why": "A ::ng-deep reach into ds-card's inner .card to clip a full-bleed child (an image or footer strip) inside the card radius, because no token exposed it.",
170
+ "replaceWith": "--ds-card-overflow: clip on the card (clip, not hidden — it keeps the card from becoming a scroll container)"
171
+ },
172
+ {
173
+ "id": "row-menu-view-details-duplicate",
174
+ "surface": "template",
175
+ "find": [
176
+ "View Details",
177
+ "ds-menu-item",
178
+ "rowActions"
179
+ ],
180
+ "why": "A \"View Details\" entry in a row overflow menu that only repeats where the row already leads. It existed because the row click was the sole, invisible way in; a naming column with `link` makes the destination a real anchor, so the menu entry is a second control for the same navigation.",
181
+ "replaceWith": "set `link` on the column that names the record, and delete the menu item"
182
+ },
183
+ {
184
+ "id": "button-resting-shadow-ng-deep",
185
+ "surface": "style",
186
+ "find": [
187
+ "::ng-deep ds-button button",
188
+ "ds-button button",
189
+ "box-shadow"
190
+ ],
191
+ "why": "A deep selector into ds-button's inner <button> kept alive only by a resting box-shadow — background, colour, weight and border already had tokens.",
192
+ "replaceWith": "--ds-button-shadow (and --ds-button-shadow-hover) on the ds-button host"
193
+ },
194
+ {
195
+ "id": "button-disabled-reason-tooltip",
196
+ "surface": "template",
197
+ "find": [
198
+ "dsTooltip",
199
+ "ds-button",
200
+ "disabled"
201
+ ],
202
+ "why": "A tooltip on a disabled ds-button used to carry the reason it is refused. It reaches a mouse only: a natively disabled button never takes focus, so a keyboard user gets nothing and a screen reader gets no description. Applies to the tooltip that EXPLAINS the refusal, not to one that merely names the action - leave the latter alone.",
203
+ "replaceWith": "[disabledReason]=\"'...'\" on the ds-button for a standing refusal (no permission, no integration); for a refusal the user can lift by filling the form in, drop `disabled` altogether and use [error]/[warning]/[hint] with validity judged in the submit handler"
204
+ },
205
+ {
206
+ "id": "table-footer-padding-workaround",
207
+ "surface": "style",
208
+ "find": [
209
+ "pagination-footer",
210
+ "TODO(ds-table-footer-padding)"
211
+ ],
212
+ "why": "A local rule padding ds-table's `.pagination-footer`, added because the component gave it a top inset only — so the summary line sat left of the column text and on the container's border. The footer is inset by the cells' own padding now, and a local rule DOUBLES it.",
213
+ "replaceWith": "nothing — and retune both together through --ds-table-cell-pad-x if the inset is wrong for you"
214
+ }
215
+ ]
216
+ }
@@ -0,0 +1,305 @@
1
+ {
2
+ "version": "0.11.1",
3
+ "items": [
4
+ {
5
+ "id": "autocomplete-panel-classes-renamed",
6
+ "kind": "class-rename",
7
+ "old": ".autocomplete-list, .autocomplete-optgroup, .autocomplete-optgroup-label, and the check icon's .icon inside an option",
8
+ "new": ".dropdown-list, .optgroup, .optgroup-label, .option-check — all inside a new .dropdown-panel wrapper",
9
+ "appliesWhen": "You wrote a global rule against `.ds-overlay-pane .autocomplete-list` or a sibling. Nothing to do if you only use the `<ds-autocomplete>` element and its inputs.",
10
+ "pitfall": "The panel is portaled to document.body, so these rules are almost always global rather than component-scoped — grep your global stylesheets, not just the component next to the picker.",
11
+ "searchHints": [
12
+ "autocomplete-list",
13
+ "autocomplete-optgroup"
14
+ ],
15
+ "surface": "style",
16
+ "detect": [
17
+ ".autocomplete-list",
18
+ ".autocomplete-optgroup",
19
+ ".autocomplete-optgroup-label"
20
+ ],
21
+ "verify": "The autocomplete's open panel carries `ds-dropdown-panel` on its `.cdk-overlay-pane`, and its rows have 4px padding and a 4px radius without any rule of yours.",
22
+ "restore": null,
23
+ "note": "The panel now renders through the same shared partial as ds-select and ds-multi-select, so it inherits their padding, row radius, selected-row hooks and pressed states. An override that existed only to close that gap is dead weight, and one that names an old class silently stops matching.",
24
+ "action": "Retarget every rule that names an old class, then delete the ones that only restored padding or row radius."
25
+ },
26
+ {
27
+ "id": "autocomplete-option-hover-token-removed",
28
+ "kind": "token-rename",
29
+ "old": "--ds-autocomplete-option-bg-color-hover",
30
+ "new": "--ds-option-selected-bg-color, --ds-option-selected-label-color, --ds-option-selected-bg-color-hover, --ds-option-check-color",
31
+ "appliesWhen": "You set --ds-autocomplete-option-bg-color-hover anywhere.",
32
+ "pitfall": "The old token painted BOTH the hover and the selected row, because the autocomplete had no separate selected treatment. The panel-level hooks separate them, so a single old value may need splitting across two.",
33
+ "searchHints": [
34
+ "ds-autocomplete-option-bg-color-hover"
35
+ ],
36
+ "surface": "style",
37
+ "detect": [
38
+ "--ds-autocomplete-option-bg-color-hover"
39
+ ],
40
+ "verify": "A :root or ds-autocomplete override of --ds-option-selected-bg-color repaints the selected row in ds-select and ds-autocomplete. ds-multi-select marks selection with a checkbox, so it answers to --ds-multi-select-check-* instead.",
41
+ "restore": null,
42
+ "note": "The autocomplete had no separate selected treatment, so one token painted both hover and selection. The panel-level hooks reach all three pickers and separate the two states, which is what the 0.9.0 notes already claimed was true.",
43
+ "action": "Replace --ds-autocomplete-option-bg-color-hover with the panel-level --ds-option-* hooks."
44
+ },
45
+ {
46
+ "id": "autocomplete-single-value-ellipsizes",
47
+ "kind": "behavior",
48
+ "old": "A settled single value wider than the trigger wrapped onto a second line and pushed the chevron onto a third — measured 40px to 63px at a 144px trigger.",
49
+ "new": null,
50
+ "appliesWhen": "You use `<ds-autocomplete>` in single mode in a narrow column.",
51
+ "pitfall": "Multi mode is unchanged — its chips already had a measured cap. This only affects the settled single value.",
52
+ "searchHints": [
53
+ "ds-autocomplete"
54
+ ],
55
+ "surface": "template",
56
+ "detect": [
57
+ "<ds-autocomplete"
58
+ ],
59
+ "verify": "A long value in a 144px-wide single-select autocomplete keeps the trigger one row tall and ends in an ellipsis, with the full text on the element's title.",
60
+ "restore": "valueOverflow=\"wrap\"",
61
+ "note": "A settled single value now clips with an ellipsis and keeps the trigger one row tall, with the full text on the element title. Multi mode is untouched — its chips already had a measured cap. Nothing in your markup has to change unless the wrapping was deliberate.",
62
+ "action": "Do nothing, or set valueOverflow=\"wrap\" on the pickers that relied on the value wrapping."
63
+ },
64
+ {
65
+ "id": "exported-class-members-grew",
66
+ "kind": "behavior",
67
+ "old": "class MySelect extends SelectComponent, class MyMultiSelect extends MultiSelectComponent, class MyAutocomplete extends AutocompleteComponent",
68
+ "new": null,
69
+ "appliesWhen": "Subclassing a DS component is unsupported, but consumers do it. Template users of the `<ds-…>` elements need nothing.",
70
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
71
+ "searchHints": [
72
+ "extends SelectComponent",
73
+ "extends MultiSelectComponent",
74
+ "extends AutocompleteComponent"
75
+ ],
76
+ "surface": "typescript",
77
+ "detect": [
78
+ "extends SelectComponent",
79
+ "extends MultiSelectComponent",
80
+ "extends AutocompleteComponent"
81
+ ],
82
+ "verify": "The app builds with no TS2415 or TS2416 naming a picker component.",
83
+ "restore": null,
84
+ "note": "All three pickers gained members: ds-select a width input and a private panelTokens field, ds-multi-select and ds-autocomplete a label/required/optional block plus projection slots. Subclassing a DS component is unsupported but consumers do it, and a redeclared member collides whether it is public or protected. The compiler enumerates every collision, so a build is the whole check and no list here could stay current.",
85
+ "action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding."
86
+ },
87
+ {
88
+ "id": "autocomplete-width-type-widened",
89
+ "kind": "behavior",
90
+ "old": "export type AutocompleteWidth = 'fill' | 'content';",
91
+ "new": null,
92
+ "appliesWhen": "You import AutocompleteWidth by name.",
93
+ "pitfall": "Only a declaration that re-declares the type structurally (rather than importing it) could notice, and it still sees the same union.",
94
+ "searchHints": [
95
+ "AutocompleteWidth"
96
+ ],
97
+ "surface": "typescript",
98
+ "detect": [
99
+ "AutocompleteWidth"
100
+ ],
101
+ "verify": "The app builds and `width` still accepts only 'fill' and 'content'.",
102
+ "restore": null,
103
+ "note": "AutocompleteWidth is now an alias of the shared DsControlWidth that SelectWidth and MultiSelectWidth also alias. The union it resolves to is unchanged, so an import keeps compiling and `width` still accepts exactly `fill` and `content`.",
104
+ "action": "Do nothing."
105
+ },
106
+ {
107
+ "id": "autocomplete-option-groups-input-removed",
108
+ "kind": "input-rename",
109
+ "old": "optionGroups",
110
+ "new": "options",
111
+ "action": "Move the array you passed to `optionGroups` into `options`.",
112
+ "note": "The autocomplete took groups in a second input and documented `options` as ignored whenever it was set, so two inputs existed and one silently won. `options` now accepts flat options, groups, or both mixed, in the order given, which is the shape ds-select already used and ds-multi-select has gained.",
113
+ "appliesWhen": "You bind `[optionGroups]` on a `<ds-autocomplete>`.",
114
+ "pitfall": "If you were passing BOTH inputs and relying on the flat one being dropped, merging them changes what renders — the flat options now appear alongside the groups rather than vanishing.",
115
+ "searchHints": [
116
+ "optionGroups"
117
+ ],
118
+ "surface": "template",
119
+ "detect": [
120
+ "[optionGroups]",
121
+ "optionGroups="
122
+ ],
123
+ "verify": "The autocomplete renders its labelled sections with only `options` bound, and filtering still hides a group whose options all fail the query.",
124
+ "restore": null
125
+ },
126
+ {
127
+ "id": "multi-select-panel-classes-renamed",
128
+ "kind": "class-rename",
129
+ "old": ".panel, .options (inside ds-multi-select’s portaled panel)",
130
+ "new": ".dropdown-panel, .dropdown-list",
131
+ "action": "Retarget any rule naming the old classes, then delete the ones that only restored what the shared panel already gives.",
132
+ "note": "The multi-select carried its own copy of the panel and the option row while its pane also carried ds-dropdown-panel, so both rule sets applied at once and the component’s won. It renders through the shared partial now, like the other two pickers.",
133
+ "appliesWhen": "You wrote a global rule against `.ds-overlay-pane .panel` or `.options` for the multi-select.",
134
+ "pitfall": "The panel is portaled to document.body, so such a rule is almost always global rather than beside the component.",
135
+ "searchHints": [
136
+ "ds-overlay-pane .panel",
137
+ ".options"
138
+ ],
139
+ "surface": "style",
140
+ "detect": [
141
+ ".ds-overlay-pane .panel",
142
+ ".ds-overlay-pane .options"
143
+ ],
144
+ "verify": "The multi-select panel renders with 4px padding and 4px row radius with no rule of yours, and its rows pick up the shared partial’s hover and active fills.",
145
+ "restore": null
146
+ },
147
+ {
148
+ "id": "trigger-display-compact-renamed",
149
+ "kind": "value-remap",
150
+ "old": "triggerDisplay=\"compact\"",
151
+ "new": "triggerDisplay=\"count\"",
152
+ "map": {
153
+ "compact": "count"
154
+ },
155
+ "action": "Replace the value `compact` with `count`.",
156
+ "note": "A third value, `labels`, now sits beside it and names the selection instead of counting it, so the old name no longer said which of the two it was.",
157
+ "appliesWhen": "You set triggerDisplay on a ds-multi-select. The input shipped inside this same unreleased block, so only work in flight is affected.",
158
+ "pitfall": "None — the rendering of `count` is exactly what `compact` did.",
159
+ "searchHints": [
160
+ "triggerDisplay"
161
+ ],
162
+ "surface": "template",
163
+ "detect": [
164
+ "triggerDisplay=\"compact\"",
165
+ "triggerDisplay: 'compact'"
166
+ ],
167
+ "verify": "The trigger still shows a caption and a count badge.",
168
+ "restore": null
169
+ },
170
+ {
171
+ "id": "published-manifest-corrections",
172
+ "kind": "behavior",
173
+ "old": "a repo upgraded through 0.5.1, 0.9.0 or 0.10.1 before this release",
174
+ "new": null,
175
+ "surface": [
176
+ "template",
177
+ "typescript",
178
+ "style"
179
+ ],
180
+ "action": "Re-run three items whose earlier text could not do its job. 0.5.1#progress-variant-remap: search for `variant=\"warn\"` and `variant=\"indeterminate\"` on ds-progress and for `ProgressVariant` in TypeScript, and finish that remap — the colour vocabulary is `default | success | warning | error` and the indeterminate state is the bare `indeterminate` attribute. 0.9.0#search-height-joins-field-scale: search for `--hit-min` and drop the pin where it was set only to shorten a ds-search row. 0.10.1: search for `(closed)` on a modal whose body holds a ds-date-picker and keep the body mounted instead.",
181
+ "appliesWhen": "Only if your last upgrade ran BEFORE this release and crossed 0.5.1, 0.9.0 or 0.10.1. A first-time consumer, or one whose upgrade runs from here on, reads the corrected files and needs none of this. The three are independent — crossing 0.5.1 says nothing about 0.10.1.",
182
+ "pitfall": "The 0.5.1 one is the silent case: its old check inspected ds-badge chips and the status registry, so it passed on a ds-progress that was never migrated. A clean upgrade report from that run proves nothing about ds-progress, so search rather than trusting it. The other two leave redundant code, not broken code — a `--hit-min` pin set deliberately for density is not this, so read each hit before deleting it.",
183
+ "note": "These manifests are executed by an upgrade tool, so a wrong verify or a locator that finds nothing lands in the consumer repo as an unapplied migration that reported success.",
184
+ "searchHints": [
185
+ "variant=\"warn\"",
186
+ "variant=\"indeterminate\"",
187
+ "ProgressVariant",
188
+ "--hit-min",
189
+ "ds-progress",
190
+ "(closed)"
191
+ ],
192
+ "detect": [
193
+ "variant=\"warn\"",
194
+ "variant=\"indeterminate\"",
195
+ "ProgressVariant",
196
+ "--hit-min",
197
+ "@if (open())"
198
+ ],
199
+ "verify": "No ds-progress binds `variant=\"warn\"` or `variant=\"indeterminate\"` and nothing is typed against a removed ProgressVariant member; no `--hit-min` pin exists whose only purpose was a shorter ds-search row; no modal body is torn down on `(closed)` to reset a ds-date-picker.",
200
+ "restore": null,
201
+ "supersedes": null
202
+ },
203
+ {
204
+ "id": "autocomplete-options-element-type-widened",
205
+ "kind": "behavior",
206
+ "old": "ds-autocomplete [options] typed readonly AutocompleteOption<T>[]",
207
+ "new": null,
208
+ "surface": "typescript",
209
+ "action": "Only where you READ the array back or type a variable against its element: change `AutocompleteOption<T>` to `AutocompleteItem<T>` and narrow each element with `isDsOptionGroup` before touching `.value`. Narrow before reading: `for (const item of picker.options()) { if (isDsOptionGroup(item)) continue; /* item.value is safe here */ }`. `isDsOptionGroup` and `flattenDsOptions` are exported from the package root.",
210
+ "appliesWhen": "Only code that reads the input back, declares a variable or field typed against its element, or overrides a member typed that way. Passing plain options IN is unchanged and needs nothing — a template binding is unaffected.",
211
+ "pitfall": "The compiler catches the type, not the assumption. Code that already destructures `.value` off each element keeps compiling wherever the variable is inferred rather than annotated, and then reads `undefined` at runtime for a group.",
212
+ "note": "The element type is now `AutocompleteItem<T>`. The input takes flat options, groups, or both mixed, so an element is no longer always an option.",
213
+ "searchHints": [
214
+ "AutocompleteOption",
215
+ "AutocompleteItem",
216
+ "ds-autocomplete",
217
+ "[options]",
218
+ "isDsOptionGroup"
219
+ ],
220
+ "detect": [
221
+ "AutocompleteOption<",
222
+ ": AutocompleteOption",
223
+ "AutocompleteOption[]"
224
+ ],
225
+ "verify": "No variable, field or override is typed `AutocompleteOption` where it receives the contents of an `options` array, and every `.value` read off such an element is guarded by `isDsOptionGroup`.",
226
+ "restore": null,
227
+ "supersedes": null
228
+ },
229
+ {
230
+ "id": "multi-select-options-element-type-widened",
231
+ "kind": "behavior",
232
+ "old": "ds-multi-select [options] typed readonly MultiSelectOption[]",
233
+ "new": null,
234
+ "surface": "typescript",
235
+ "action": "Only where you READ the array back or type a variable against its element: change `MultiSelectOption` to `MultiSelectItem` and narrow with `isDsOptionGroup` before touching `.value`. Narrow before reading: `for (const item of picker.options()) { if (isDsOptionGroup(item)) continue; /* item.value is safe here */ }`. `isDsOptionGroup` and `flattenDsOptions` are exported from the package root.",
236
+ "appliesWhen": "Only code that reads the input back, declares a variable or field typed against its element, or overrides a member typed that way. Passing plain options IN is unchanged.",
237
+ "pitfall": "ds-multi-select accepted no groups at all before this release, so existing code has no reason to guard and every element really was an option. That is exactly why the read sites are worth finding rather than trusting.",
238
+ "note": "The element type is now `MultiSelectItem`. Groups are new on this component, so the element union is new here too.",
239
+ "searchHints": [
240
+ "MultiSelectOption",
241
+ "MultiSelectItem",
242
+ "ds-multi-select",
243
+ "[options]",
244
+ "isDsOptionGroup"
245
+ ],
246
+ "detect": [
247
+ "MultiSelectOption<",
248
+ ": MultiSelectOption",
249
+ "MultiSelectOption[]"
250
+ ],
251
+ "verify": "No variable, field or override is typed `MultiSelectOption` where it receives the contents of an `options` array, and every `.value` read off such an element is guarded by `isDsOptionGroup`.",
252
+ "restore": null,
253
+ "supersedes": null
254
+ },
255
+ {
256
+ "id": "multi-select-select-all-type-widened",
257
+ "kind": "behavior",
258
+ "old": "ds-multi-select selectAll typed boolean",
259
+ "new": null,
260
+ "surface": "typescript",
261
+ "action": "Only where you READ `selectAll` back into a `boolean`: widen the receiving type to `boolean | 'group' | 'both'`, or compare against the value you meant (`selectAll() === true`).",
262
+ "appliesWhen": "Only code that assigns the input back into a `boolean`, or a subclass that re-declares it. Setting it — `[selectAll]=\"true\"` or the bare attribute — is unchanged, and the default is still `false`.",
263
+ "pitfall": "A truthiness test that used to mean \"the whole panel\" now also passes for `'group'`, where there is no panel-wide row at all — so a guard written as `if (selectAll())` silently changes meaning while still compiling.",
264
+ "note": "The type is now `boolean | 'group' | 'both'`. `'group'` renders a row per group and `'both'` adds the panel-wide row beside them.",
265
+ "searchHints": [
266
+ "selectAll",
267
+ "ds-multi-select",
268
+ "'group'",
269
+ "'both'"
270
+ ],
271
+ "detect": [
272
+ "selectAll()",
273
+ "[selectAll]",
274
+ "selectAll:"
275
+ ],
276
+ "verify": "Nothing assigns `selectAll` into a `boolean`, and any truthiness test on it has been read once to confirm it still means what it did.",
277
+ "restore": null,
278
+ "supersedes": null
279
+ }
280
+ ],
281
+ "informational": [
282
+ "ds-multi-select and ds-select gained `width`, the input ds-autocomplete already had: `content` takes the trigger width as the panel's floor instead of its width, so a short trigger stops forcing an unreadable panel. Default `fill` is unchanged.",
283
+ "New panel bounds for that mode: --ds-dropdown-panel-minw and --ds-dropdown-panel-maxw.",
284
+ "ds-select now forwards its panel custom properties onto the portaled pane, which it never did — a `ds-select { --ds-dropdown-panel-*: … }` reaches the panel now instead of being silently dropped.",
285
+ "ds-multi-select gained option groups, which it never had. A group disables all of its options when its own `disabled` is set.",
286
+ "ds-multi-select and ds-autocomplete gained `label`, `required` and `optional`, which existed on ds-select alone; ds-multi-select gained `size`, which the other two already had.",
287
+ "New slots: dsEmptyTemplate on all three pickers, dsCreateTemplate on ds-autocomplete. ds-select shows an empty row when it has no options, where it used to open a blank panel.",
288
+ "selectAll on ds-multi-select accepts 'group' and 'both' beside true/false.",
289
+ "All three pickers now forward the four panel-level --ds-option-* hooks onto their portaled pane, so a per-instance override reaches the panel.",
290
+ "The dropdown panel geometry now lives only in styles/_dropdown-overlay.scss, behind --ds-dropdown-panel-bg-color/-radius/-maxh/-minw/-maxw. The per-picker names (--ds-multi-select-panel-bg-color, --ds-autocomplete-panel-bg-color/-radius/-maxh) are aliases of those and still work; a global rule of yours that relied on a component stylesheet out-ranking the partial no longer has a competing rule to beat."
291
+ ],
292
+ "deleteList": [
293
+ {
294
+ "id": "autocomplete-listbox-padding-override",
295
+ "surface": "style",
296
+ "find": [
297
+ ".ds-overlay-pane .autocomplete-list",
298
+ "padding",
299
+ "border-radius"
300
+ ],
301
+ "why": "The autocomplete panel shipped with `padding: 0` and square rows while ds-select's dropdown had `--space-1` padding and rounded rows, so consumers patched the difference globally. The panel now uses the same shared partial as the other two pickers and matches without help.",
302
+ "replaceWith": "Nothing — delete the rule. The padding is --space-1 and the row radius is --ds-radius-inner out of the box; --ds-dropdown-panel-minw / -maxw are there if you want to bound the panel."
303
+ }
304
+ ]
305
+ }
@@ -6,7 +6,7 @@
6
6
  "kind": "token-rename",
7
7
  "old": "--border-subtle",
8
8
  "new": "--border-subtitle",
9
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename (8 families).",
9
+ "action": "Replace `--border-subtle` with `--border-subtitle`.",
10
10
  "searchHints": [
11
11
  "--border-subtle"
12
12
  ],
@@ -17,7 +17,7 @@
17
17
  "kind": "token-rename",
18
18
  "old": "--primary-subtle",
19
19
  "new": "--primary-subtitle",
20
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename.",
20
+ "action": "Replace `--primary-subtle` with `--primary-subtitle`.",
21
21
  "searchHints": [
22
22
  "--primary-subtle"
23
23
  ],
@@ -28,7 +28,7 @@
28
28
  "kind": "token-rename",
29
29
  "old": "--secondary-subtle",
30
30
  "new": "--secondary-subtitle",
31
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename.",
31
+ "action": "Replace `--secondary-subtle` with `--secondary-subtitle`.",
32
32
  "searchHints": [
33
33
  "--secondary-subtle"
34
34
  ],
@@ -39,18 +39,29 @@
39
39
  "kind": "token-rename",
40
40
  "old": "--tertiary-subtle",
41
41
  "new": "--tertiary-subtitle",
42
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename.",
42
+ "action": "Replace `--tertiary-subtle` with `--tertiary-subtitle`.",
43
43
  "searchHints": [
44
44
  "--tertiary-subtle"
45
45
  ],
46
46
  "surface": "style"
47
47
  },
48
+ {
49
+ "id": "surface-subtle-token-rename",
50
+ "kind": "token-rename",
51
+ "old": "--surface-subtle",
52
+ "new": "--surface-subtitle",
53
+ "action": "Replace `--surface-subtle` with `--surface-subtitle`.",
54
+ "searchHints": [
55
+ "--surface-subtle"
56
+ ],
57
+ "surface": "style"
58
+ },
48
59
  {
49
60
  "id": "success-subtle-token-rename",
50
61
  "kind": "token-rename",
51
62
  "old": "--success-subtle",
52
63
  "new": "--success-subtitle",
53
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename.",
64
+ "action": "Replace `--success-subtle` with `--success-subtitle`.",
54
65
  "searchHints": [
55
66
  "--success-subtle"
56
67
  ],
@@ -61,7 +72,7 @@
61
72
  "kind": "token-rename",
62
73
  "old": "--warning-subtle",
63
74
  "new": "--warning-subtitle",
64
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename.",
75
+ "action": "Replace `--warning-subtle` with `--warning-subtitle`.",
65
76
  "searchHints": [
66
77
  "--warning-subtle"
67
78
  ],
@@ -72,7 +83,7 @@
72
83
  "kind": "token-rename",
73
84
  "old": "--error-subtle",
74
85
  "new": "--error-subtitle",
75
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename.",
86
+ "action": "Replace `--error-subtle` with `--error-subtitle`.",
76
87
  "searchHints": [
77
88
  "--error-subtle"
78
89
  ],
@@ -83,7 +94,7 @@
83
94
  "kind": "token-rename",
84
95
  "old": "--info-subtle",
85
96
  "new": "--info-subtitle",
86
- "note": "Part of the --*-subtle -> --*-subtitle semantic-token rename.",
97
+ "action": "Replace `--info-subtle` with `--info-subtitle`.",
87
98
  "searchHints": [
88
99
  "--info-subtle"
89
100
  ],
@@ -91,7 +102,9 @@
91
102
  }
92
103
  ],
93
104
  "informational": [
105
+ "All nine `--*-subtle` semantic tokens became `--*-subtitle` in this release - border, primary, secondary, tertiary, surface, success, warning, error and info. Each has its own item above; no token keeps the old spelling, and no longer token is built on one of these names, so the nine renames are independent and can be applied in any order.",
94
106
  "Theme re-skin guidance clarified in the shipped themes/README (brand roles retint from the --blue ramp; a fully calibrated brand may set --primary-* roles directly).",
95
107
  "Relicensed from proprietary (UNLICENSED) to MIT."
96
- ]
108
+ ],
109
+ "deleteList": []
97
110
  }
@@ -3,5 +3,6 @@
3
3
  "items": [],
4
4
  "informational": [
5
5
  "Added a homepage field linking the live docs/showcase so the npm package page points to it. No consumer action."
6
- ]
6
+ ],
7
+ "deleteList": []
7
8
  }