@ids-group-ltd/ids-design-system 0.11.0 → 0.11.2
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.
- package/CHANGELOG.md +1368 -1021
- package/components.md +49 -26
- package/design-system.md +18 -18
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +1750 -598
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.10.0.json +19 -19
- package/migrations/0.10.1.json +20 -7
- package/migrations/0.10.2.json +8 -8
- package/migrations/0.10.3.json +2 -2
- package/migrations/0.11.0.json +9 -54
- package/migrations/0.11.1.json +279 -0
- package/migrations/0.11.2.json +158 -0
- package/migrations/0.2.0.json +17 -5
- package/migrations/0.2.2.json +1 -1
- package/migrations/0.3.0.json +1 -1
- package/migrations/0.4.0.json +1 -1
- package/migrations/0.5.1/badge-statuses.md +1 -3
- package/migrations/0.5.1.json +1 -1
- package/migrations/0.6.3.json +1 -1
- package/migrations/0.7.1.json +6 -6
- package/migrations/0.8.0.json +5 -5
- package/migrations/0.9.0.json +12 -11
- package/migrations/0.9.1.json +2 -2
- package/migrations/README.md +34 -52
- package/package.json +1 -1
- package/styles/_dropdown-overlay.scss +64 -23
- package/styles/_ds-color.scss +3 -3
- package/styles/_field-box.scss +2 -6
- package/styles/_field-label.scss +5 -10
- package/styles/_field-state.scss +3 -2
- package/styles/_focus.scss +0 -2
- package/styles/_layout-utils.scss +2 -2
- package/styles/_overlay-motion.scss +2 -3
- package/styles/_press.scss +3 -5
- package/styles/_reset.scss +0 -1
- package/styles/_scrollbar.scss +1 -3
- package/styles/_status.scss +1 -2
- package/styles/_surface-motion.scss +3 -4
- package/styles/_text-clip.scss +1 -1
- package/styles/_theme-activation.scss +1 -1
- package/styles/_tokens-charts.scss +1 -3
- package/styles/_tokens.scss +5 -4
- package/styles/_typography.scss +2 -2
- package/themes/README.md +6 -6
- package/themes/_base-palette.scss +2 -2
- package/themes/_semantic.scss +2 -2
- package/themes/dark/_palette.scss +1 -2
- package/themes/light/_palette.scss +1 -1
- package/themes/light/_theme.scss +1 -1
- package/types/ids-group-ltd-ids-design-system.d.ts +608 -72
|
@@ -0,0 +1,279 @@
|
|
|
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. Separately, seven symbols are newly exported and can shadow a local name of the same spelling rather than collide with a member: `DsControlWidth`, `DsTriggerDisplay`, `DsChipTemplateDirective`, `DsCreateTemplateDirective`, `DsEmptyTemplateDirective`, `DsOptionTemplateDirective`, `DsPickerTriggerDirective`. Those are new names, not changed ones — nothing of yours breaks unless you already had one.",
|
|
71
|
+
"searchHints": [
|
|
72
|
+
"extends SelectComponent",
|
|
73
|
+
"extends MultiSelectComponent",
|
|
74
|
+
"extends AutocompleteComponent",
|
|
75
|
+
"DsControlWidth",
|
|
76
|
+
"DsTriggerDisplay",
|
|
77
|
+
"DsChipTemplateDirective",
|
|
78
|
+
"DsCreateTemplateDirective",
|
|
79
|
+
"DsEmptyTemplateDirective",
|
|
80
|
+
"DsOptionTemplateDirective",
|
|
81
|
+
"DsPickerTriggerDirective"
|
|
82
|
+
],
|
|
83
|
+
"surface": "typescript",
|
|
84
|
+
"detect": [
|
|
85
|
+
"extends SelectComponent",
|
|
86
|
+
"extends MultiSelectComponent",
|
|
87
|
+
"extends AutocompleteComponent"
|
|
88
|
+
],
|
|
89
|
+
"verify": "The app builds with no TS2415 or TS2416 naming a picker component.",
|
|
90
|
+
"restore": null,
|
|
91
|
+
"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.",
|
|
92
|
+
"action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding."
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"id": "autocomplete-width-type-widened",
|
|
96
|
+
"kind": "behavior",
|
|
97
|
+
"old": "export type AutocompleteWidth = 'fill' | 'content';",
|
|
98
|
+
"new": null,
|
|
99
|
+
"appliesWhen": "You import AutocompleteWidth by name.",
|
|
100
|
+
"pitfall": "Only a declaration that re-declares the type structurally (rather than importing it) could notice, and it still sees the same union.",
|
|
101
|
+
"searchHints": [
|
|
102
|
+
"AutocompleteWidth"
|
|
103
|
+
],
|
|
104
|
+
"surface": "typescript",
|
|
105
|
+
"detect": [
|
|
106
|
+
"AutocompleteWidth"
|
|
107
|
+
],
|
|
108
|
+
"verify": "The app builds and `width` still accepts only 'fill' and 'content'.",
|
|
109
|
+
"restore": null,
|
|
110
|
+
"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`.",
|
|
111
|
+
"action": "Do nothing."
|
|
112
|
+
},
|
|
113
|
+
{
|
|
114
|
+
"id": "autocomplete-option-groups-input-removed",
|
|
115
|
+
"kind": "input-rename",
|
|
116
|
+
"old": "optionGroups",
|
|
117
|
+
"new": "options",
|
|
118
|
+
"action": "Move the array you passed to `optionGroups` into `options`.",
|
|
119
|
+
"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.",
|
|
120
|
+
"appliesWhen": "You bind `[optionGroups]` on a `<ds-autocomplete>`.",
|
|
121
|
+
"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.",
|
|
122
|
+
"searchHints": [
|
|
123
|
+
"optionGroups"
|
|
124
|
+
],
|
|
125
|
+
"surface": "template",
|
|
126
|
+
"detect": [
|
|
127
|
+
"[optionGroups]",
|
|
128
|
+
"optionGroups="
|
|
129
|
+
],
|
|
130
|
+
"verify": "The autocomplete renders its labelled sections with only `options` bound, and filtering still hides a group whose options all fail the query.",
|
|
131
|
+
"restore": null
|
|
132
|
+
},
|
|
133
|
+
{
|
|
134
|
+
"id": "multi-select-panel-classes-renamed",
|
|
135
|
+
"kind": "class-rename",
|
|
136
|
+
"old": ".panel, .options (inside ds-multi-select’s portaled panel)",
|
|
137
|
+
"new": ".dropdown-panel, .dropdown-list",
|
|
138
|
+
"action": "Retarget any rule naming the old classes, then delete the ones that only restored what the shared panel already gives.",
|
|
139
|
+
"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.",
|
|
140
|
+
"appliesWhen": "You wrote a global rule against `.ds-overlay-pane .panel` or `.options` for the multi-select.",
|
|
141
|
+
"pitfall": "The panel is portaled to document.body, so such a rule is almost always global rather than beside the component.",
|
|
142
|
+
"searchHints": [
|
|
143
|
+
"ds-overlay-pane .panel",
|
|
144
|
+
".options"
|
|
145
|
+
],
|
|
146
|
+
"surface": "style",
|
|
147
|
+
"detect": [
|
|
148
|
+
".ds-overlay-pane .panel",
|
|
149
|
+
".ds-overlay-pane .options"
|
|
150
|
+
],
|
|
151
|
+
"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.",
|
|
152
|
+
"restore": null
|
|
153
|
+
},
|
|
154
|
+
{
|
|
155
|
+
"id": "trigger-display-compact-renamed",
|
|
156
|
+
"kind": "value-remap",
|
|
157
|
+
"old": "triggerDisplay=\"compact\"",
|
|
158
|
+
"new": "triggerDisplay=\"count\"",
|
|
159
|
+
"map": {
|
|
160
|
+
"compact": "count"
|
|
161
|
+
},
|
|
162
|
+
"action": "Replace the value `compact` with `count`.",
|
|
163
|
+
"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.",
|
|
164
|
+
"appliesWhen": "You set triggerDisplay on a ds-multi-select. The input shipped inside this same unreleased block, so only work in flight is affected.",
|
|
165
|
+
"pitfall": "None — the rendering of `count` is exactly what `compact` did.",
|
|
166
|
+
"searchHints": [
|
|
167
|
+
"triggerDisplay"
|
|
168
|
+
],
|
|
169
|
+
"surface": "template",
|
|
170
|
+
"detect": [
|
|
171
|
+
"triggerDisplay=\"compact\"",
|
|
172
|
+
"triggerDisplay: 'compact'"
|
|
173
|
+
],
|
|
174
|
+
"verify": "The trigger still shows a caption and a count badge.",
|
|
175
|
+
"restore": null
|
|
176
|
+
},
|
|
177
|
+
{
|
|
178
|
+
"id": "autocomplete-options-element-type-widened",
|
|
179
|
+
"kind": "behavior",
|
|
180
|
+
"old": "ds-autocomplete [options] typed readonly AutocompleteOption<T>[]",
|
|
181
|
+
"new": null,
|
|
182
|
+
"surface": "typescript",
|
|
183
|
+
"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.",
|
|
184
|
+
"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.",
|
|
185
|
+
"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.",
|
|
186
|
+
"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.",
|
|
187
|
+
"searchHints": [
|
|
188
|
+
"AutocompleteOption",
|
|
189
|
+
"AutocompleteItem",
|
|
190
|
+
"ds-autocomplete",
|
|
191
|
+
"[options]",
|
|
192
|
+
"isDsOptionGroup"
|
|
193
|
+
],
|
|
194
|
+
"detect": [
|
|
195
|
+
"AutocompleteOption<",
|
|
196
|
+
": AutocompleteOption",
|
|
197
|
+
"AutocompleteOption[]"
|
|
198
|
+
],
|
|
199
|
+
"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`.",
|
|
200
|
+
"restore": null,
|
|
201
|
+
"supersedes": null
|
|
202
|
+
},
|
|
203
|
+
{
|
|
204
|
+
"id": "multi-select-options-element-type-widened",
|
|
205
|
+
"kind": "behavior",
|
|
206
|
+
"old": "ds-multi-select [options] typed readonly MultiSelectOption[]",
|
|
207
|
+
"new": null,
|
|
208
|
+
"surface": "typescript",
|
|
209
|
+
"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.",
|
|
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.",
|
|
211
|
+
"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.",
|
|
212
|
+
"note": "The element type is now `MultiSelectItem`. Groups are new on this component, so the element union is new here too.",
|
|
213
|
+
"searchHints": [
|
|
214
|
+
"MultiSelectOption",
|
|
215
|
+
"MultiSelectItem",
|
|
216
|
+
"ds-multi-select",
|
|
217
|
+
"[options]",
|
|
218
|
+
"isDsOptionGroup"
|
|
219
|
+
],
|
|
220
|
+
"detect": [
|
|
221
|
+
"MultiSelectOption<",
|
|
222
|
+
": MultiSelectOption",
|
|
223
|
+
"MultiSelectOption[]"
|
|
224
|
+
],
|
|
225
|
+
"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`.",
|
|
226
|
+
"restore": null,
|
|
227
|
+
"supersedes": null
|
|
228
|
+
},
|
|
229
|
+
{
|
|
230
|
+
"id": "multi-select-select-all-type-widened",
|
|
231
|
+
"kind": "behavior",
|
|
232
|
+
"old": "ds-multi-select selectAll typed boolean",
|
|
233
|
+
"new": null,
|
|
234
|
+
"surface": "typescript",
|
|
235
|
+
"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`).",
|
|
236
|
+
"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`.",
|
|
237
|
+
"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.",
|
|
238
|
+
"note": "The type is now `boolean | 'group' | 'both'`. `'group'` renders a row per group and `'both'` adds the panel-wide row beside them.",
|
|
239
|
+
"searchHints": [
|
|
240
|
+
"selectAll",
|
|
241
|
+
"ds-multi-select",
|
|
242
|
+
"'group'",
|
|
243
|
+
"'both'"
|
|
244
|
+
],
|
|
245
|
+
"detect": [
|
|
246
|
+
"selectAll()",
|
|
247
|
+
"[selectAll]",
|
|
248
|
+
"selectAll:"
|
|
249
|
+
],
|
|
250
|
+
"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.",
|
|
251
|
+
"restore": null,
|
|
252
|
+
"supersedes": null
|
|
253
|
+
}
|
|
254
|
+
],
|
|
255
|
+
"informational": [
|
|
256
|
+
"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.",
|
|
257
|
+
"New panel bounds for that mode: --ds-dropdown-panel-minw and --ds-dropdown-panel-maxw.",
|
|
258
|
+
"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.",
|
|
259
|
+
"ds-multi-select gained option groups, which it never had. A group disables all of its options when its own `disabled` is set.",
|
|
260
|
+
"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.",
|
|
261
|
+
"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.",
|
|
262
|
+
"selectAll on ds-multi-select accepts 'group' and 'both' beside true/false.",
|
|
263
|
+
"All three pickers now forward the four panel-level --ds-option-* hooks onto their portaled pane, so a per-instance override reaches the panel.",
|
|
264
|
+
"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."
|
|
265
|
+
],
|
|
266
|
+
"deleteList": [
|
|
267
|
+
{
|
|
268
|
+
"id": "autocomplete-listbox-padding-override",
|
|
269
|
+
"surface": "style",
|
|
270
|
+
"find": [
|
|
271
|
+
".ds-overlay-pane .autocomplete-list",
|
|
272
|
+
"padding",
|
|
273
|
+
"border-radius"
|
|
274
|
+
],
|
|
275
|
+
"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.",
|
|
276
|
+
"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."
|
|
277
|
+
}
|
|
278
|
+
]
|
|
279
|
+
}
|
|
@@ -0,0 +1,158 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.11.2",
|
|
3
|
+
"items": [
|
|
4
|
+
{
|
|
5
|
+
"id": "picker-subclass-members-grew",
|
|
6
|
+
"kind": "behavior",
|
|
7
|
+
"old": "class MySelect extends SelectComponent, class MyMultiSelect extends MultiSelectComponent, class MyAutocomplete extends AutocompleteComponent",
|
|
8
|
+
"new": null,
|
|
9
|
+
"action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding.",
|
|
10
|
+
"note": "All three pickers gained members for the new inputs and outputs. 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.",
|
|
11
|
+
"appliesWhen": "You subclass a picker component. Template users of the `<ds-...>` elements need nothing.",
|
|
12
|
+
"pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
|
|
13
|
+
"searchHints": [
|
|
14
|
+
"extends SelectComponent",
|
|
15
|
+
"extends MultiSelectComponent",
|
|
16
|
+
"extends AutocompleteComponent"
|
|
17
|
+
],
|
|
18
|
+
"surface": "typescript",
|
|
19
|
+
"detect": [
|
|
20
|
+
"extends SelectComponent",
|
|
21
|
+
"extends MultiSelectComponent",
|
|
22
|
+
"extends AutocompleteComponent"
|
|
23
|
+
],
|
|
24
|
+
"verify": "The app builds with no TS2415 or TS2416 naming a picker component.",
|
|
25
|
+
"restore": null
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"id": "table-subclass-members-grew",
|
|
29
|
+
"kind": "behavior",
|
|
30
|
+
"old": "class MyTable extends TableComponent",
|
|
31
|
+
"new": null,
|
|
32
|
+
"action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding.",
|
|
33
|
+
"note": "TableComponent gained members for row expansion: expandMode, expandAllToggle, rowExpanded, rowCollapsed and the protected helpers behind the header toggle. A redeclared member collides whether it is public or protected, and the compiler enumerates every one, so a build is the whole check.",
|
|
34
|
+
"appliesWhen": "You subclass TableComponent. Template users of `<ds-table>` need nothing.",
|
|
35
|
+
"pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
|
|
36
|
+
"searchHints": [
|
|
37
|
+
"extends TableComponent"
|
|
38
|
+
],
|
|
39
|
+
"surface": "typescript",
|
|
40
|
+
"detect": [
|
|
41
|
+
"extends TableComponent"
|
|
42
|
+
],
|
|
43
|
+
"verify": "The app builds with no TS2415 or TS2416 naming TableComponent.",
|
|
44
|
+
"restore": null
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": "loading-overlay-subclass-members-grew",
|
|
48
|
+
"kind": "behavior",
|
|
49
|
+
"old": "class MyOverlay extends LoadingOverlayComponent",
|
|
50
|
+
"new": null,
|
|
51
|
+
"action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding.",
|
|
52
|
+
"note": "LoadingOverlayComponent gained `inertContent`. A redeclared member collides whether it is public or protected, and the compiler enumerates every one, so a build is the whole check.",
|
|
53
|
+
"appliesWhen": "You subclass LoadingOverlayComponent. Template users of `<ds-loading-overlay>` need nothing.",
|
|
54
|
+
"pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
|
|
55
|
+
"searchHints": [
|
|
56
|
+
"extends LoadingOverlayComponent"
|
|
57
|
+
],
|
|
58
|
+
"surface": "typescript",
|
|
59
|
+
"detect": [
|
|
60
|
+
"extends LoadingOverlayComponent"
|
|
61
|
+
],
|
|
62
|
+
"verify": "The app builds with no TS2415 or TS2416 naming LoadingOverlayComponent.",
|
|
63
|
+
"restore": null
|
|
64
|
+
},
|
|
65
|
+
{
|
|
66
|
+
"id": "toast-region-subclass-members-grew",
|
|
67
|
+
"kind": "behavior",
|
|
68
|
+
"old": "class MyToastRegion extends ToastRegionComponent",
|
|
69
|
+
"new": null,
|
|
70
|
+
"action": "Nothing unless you subclass ToastRegionComponent and declare a member of those names: rename yours, or add `override` if you meant to replace ours.",
|
|
71
|
+
"note": "ToastRegionComponent gained six members: the fields `timers`, `position` and `newestFirst`, and the methods `show`, `startCountdown` and `clearCountdown`. The auto-dismiss countdown moved into the region, because only it knows when a toast became visible — started in the service, a toast queued behind `maxVisible` expired without ever being shown. `newestFirst` puts the newest toast nearest the anchor.",
|
|
72
|
+
"appliesWhen": "Only a class that extends ToastRegionComponent.",
|
|
73
|
+
"pitfall": "`durationMs` is now a required field on `ToastEntry`. That reaches further than subclassing, so it is its own item — see `toast-entry-duration-required`.",
|
|
74
|
+
"searchHints": [
|
|
75
|
+
"extends ToastRegionComponent",
|
|
76
|
+
"ToastRegionComponent",
|
|
77
|
+
"timers",
|
|
78
|
+
"newestFirst"
|
|
79
|
+
],
|
|
80
|
+
"surface": "typescript",
|
|
81
|
+
"detect": [
|
|
82
|
+
"extends ToastRegionComponent"
|
|
83
|
+
],
|
|
84
|
+
"verify": "Build your app: no TS4114 or TS2415 against a class extending ToastRegionComponent.",
|
|
85
|
+
"restore": null
|
|
86
|
+
},
|
|
87
|
+
{
|
|
88
|
+
"id": "toast-entry-duration-required",
|
|
89
|
+
"kind": "code-add",
|
|
90
|
+
"old": null,
|
|
91
|
+
"new": "durationMs: 5000",
|
|
92
|
+
"action": "Add `durationMs` to every hand-built `ToastEntry`: the auto-dismiss delay in ms, or `0` for indefinite. `ToastService.show()` and its variants are unaffected — they take `ToastOptions`, where `durationMs` stays optional and defaults to 5000 (0 for `loading`).",
|
|
93
|
+
"note": "`ToastEntry` gained a required `durationMs: number`. The region reads it to start the countdown when the toast becomes visible, so the field has to be on the entry rather than held in the service. `ToastOptions.durationMs` is untouched — still optional, still 5000 by default, still 0 for a loading toast — so a caller of `ToastService` needs nothing.",
|
|
94
|
+
"appliesWhen": "You reference the `ToastEntry` type — annotating a variable, building one to pass to `add()`, or mapping your own model onto it. Callers of `ToastService` need nothing.",
|
|
95
|
+
"pitfall": "The break is a compile error at the construction site, not at `add()`, so a search for `add(` finds nothing. And `0` is not the same as leaving it out: it means indefinite, so a toast written that way never dismisses itself.",
|
|
96
|
+
"searchHints": [
|
|
97
|
+
"ToastEntry",
|
|
98
|
+
"durationMs",
|
|
99
|
+
".add("
|
|
100
|
+
],
|
|
101
|
+
"surface": "typescript",
|
|
102
|
+
"detect": [
|
|
103
|
+
"ToastEntry"
|
|
104
|
+
],
|
|
105
|
+
"verify": "The app builds with no TS2741 or TS2739 naming `durationMs` on `ToastEntry`.",
|
|
106
|
+
"restore": null
|
|
107
|
+
},
|
|
108
|
+
{
|
|
109
|
+
"id": "select-option-list-caps-at-picker-maxh",
|
|
110
|
+
"kind": "behavior",
|
|
111
|
+
"old": "--ds-dropdown-panel-maxh",
|
|
112
|
+
"new": null,
|
|
113
|
+
"action": "If a ds-select has to show more than 280px of options, set `--picker-maxh` to the height you want — on the panel where only that select should change, or globally where the other two pickers should follow it.",
|
|
114
|
+
"appliesWhen": "Only ds-select, and only where the list was long enough to reach the old 320px. ds-autocomplete and ds-multi-select already capped at this value and do not move.",
|
|
115
|
+
"pitfall": "`--ds-dropdown-panel-maxh` still reads 320px and still caps the PANEL. It is the list INSIDE that stops 40px sooner now, so raising the panel knob on its own changes nothing you can see.",
|
|
116
|
+
"note": "The option list's own max-height moved into the shared panel partial, so ds-select caps its list at `--picker-maxh` (280px) where it previously ran to the panel's `--ds-dropdown-panel-maxh` (320px).",
|
|
117
|
+
"searchHints": [
|
|
118
|
+
"ds-dropdown-panel-maxh",
|
|
119
|
+
"picker-maxh",
|
|
120
|
+
"<ds-select",
|
|
121
|
+
"max-height"
|
|
122
|
+
],
|
|
123
|
+
"surface": "style",
|
|
124
|
+
"verify": "Open a ds-select with more options than fit: the list scrolls at the height you set, and one left alone shows 280px of rows.",
|
|
125
|
+
"restore": "--picker-maxh: 320px"
|
|
126
|
+
}
|
|
127
|
+
],
|
|
128
|
+
"informational": [
|
|
129
|
+
"All three pickers scroll the keyboard cursor into view by default; scrollActiveIntoView=\"false\" turns it off.",
|
|
130
|
+
"Home and End now work on ds-multi-select and ds-autocomplete, which only ds-select had.",
|
|
131
|
+
"ds-autocomplete takes compareWith for object values; the default stays === so string and number values are unaffected.",
|
|
132
|
+
"New on all three pickers: loading, opened, closed. New on the two that filter: filterWith (a predicate, or \"none\" for a server-filtered list) and filterChange.",
|
|
133
|
+
"ds-multi-select and ds-autocomplete gained name, readOnly (with its readonly binding alias) and clearable, which were ds-select-only.",
|
|
134
|
+
"New slots on all three pickers: dsPanelHeaderTemplate, dsPanelFooterTemplate, dsGroupLabelTemplate.",
|
|
135
|
+
"The option row is tokenised: --ds-option-gap, --ds-option-padding, --ds-option-radius, --ds-option-row-gap, --ds-option-bg-color-active.",
|
|
136
|
+
"ds-multi-select no longer carries its own panel rules at all; --ds-multi-select-option-bg-color-active is an alias of the shared --ds-option-bg-color-active and still works.",
|
|
137
|
+
"The select-all row now reads the option row's gap and padding, so it lines up with the options below it; it was one step wider before.",
|
|
138
|
+
"DsOption gained disabledReason, so it type-checks on all three pickers. ds-select renders it today, announced through aria-describedby on the disabled row; ds-multi-select and ds-autocomplete accept the field and do not yet show it.",
|
|
139
|
+
"Type-ahead is on ds-select and ds-multi-select, not ds-autocomplete, whose trigger is a text field.",
|
|
140
|
+
"PageUp and PageDown move the cursor ten rows on all three pickers; none had them.",
|
|
141
|
+
"clear() is public on all three pickers now; it empties the value and does not move focus.",
|
|
142
|
+
"scrollActiveIntoView follows the KEYBOARD only — the rows also set the active index on mouseenter, and reacting to that pulled a half-visible row under the pointer.",
|
|
143
|
+
"aria-multiselectable stays absent from ds-select on purpose: ARIA permits it only on a multi-value listbox. docs/picker-contract.md states this so nobody adds it to satisfy the audit.",
|
|
144
|
+
"ds-table takes expandMode=\"single\" to keep one row open at a time; the default stays \"multiple\", which is what it did before.",
|
|
145
|
+
"ds-table takes expandAllToggle to put an expand-all chevron in the expander column header; it is page-scoped when paginating, like select-all, and is suppressed under expandMode=\"single\".",
|
|
146
|
+
"ds-table emits (rowExpanded) and (rowCollapsed), expand-all included. Neither fires for a collapse the host writes into expandedIds itself, nor for an id whose row is not in data().",
|
|
147
|
+
"ds-table announces \"N rows expanded\" in its live region from two rows up; a single expander already says so through its own aria-expanded.",
|
|
148
|
+
"ds-table no longer puts `skeleton-mode` on its inner `<table>` element. Nothing in the library styled it: the rule it switched on suppressed a row hover that used to reach every row, and that hover now needs `.clickable`, which a skeleton row never has. Only a consumer reaching in through ::ng-deep would notice.",
|
|
149
|
+
"The column-resize handle now carries aria-valuemin and aria-valuemax alongside aria-valuenow, all in px, while it has focus. A focusable role=\"separator\" is a range widget, so a bare pixel value was being announced against ARIA's implicit 0-100.",
|
|
150
|
+
"ds-loading-overlay now marks the content it covers `inert` while loading, so the keyboard cannot reach what the scrim already hides from the pointer. Anything focusable behind the scrim stops being tabbable and leaves the accessibility tree until loading ends; `aria-busy` on the host is unaffected.",
|
|
151
|
+
"inertContent=\"false\" on ds-loading-overlay turns that off, for a scrim that covers only part of its content — the consumer then owns marking the covered subtree. ds-table does this: its scrim starts below the header, and only `<tbody>` goes inert, so sorting and filtering during a refresh still work.",
|
|
152
|
+
"ds-table's column resize now stops at the width of the scroll viewport, on both the pointer and the keyboard path. It was unbounded before. The bound exists so the handle's aria-valuemax is true — a focusable role=\"separator\" is a range widget, and it had been announcing a ceiling nothing applied.",
|
|
153
|
+
"ds-table hides its column-resize handle under `(hover: none) and (pointer: coarse)` and puts −/+/Fit width controls in the column panel instead, which opens as a ds-bottom-sheet there. Nothing to change in a consumer app; a screenshot test taken on a touch profile will differ.",
|
|
154
|
+
"A ds-table loading scrim used to be sized to one viewport of the table and travelled with the content, so horizontal scrolling left the revealed columns uncovered. The overlay wraps the scroll container now and the scrim covers what is on screen at any offset. NO ACTION.",
|
|
155
|
+
"maxVisibleChips=\"fit\" on ds-multi-select and ds-autocomplete under-showed chips on a trigger that hugs its content: the width it measured was decided by the chips it was about to cut. It reads the space available now. A width=\"fill\" trigger is unaffected. NO ACTION."
|
|
156
|
+
],
|
|
157
|
+
"deleteList": []
|
|
158
|
+
}
|
package/migrations/0.2.0.json
CHANGED
|
@@ -48,13 +48,25 @@
|
|
|
48
48
|
{
|
|
49
49
|
"id": "surface-subtle-token-rename",
|
|
50
50
|
"kind": "token-rename",
|
|
51
|
-
"old": "
|
|
52
|
-
"new": "
|
|
53
|
-
"action": "
|
|
51
|
+
"old": "--<role>-subtle",
|
|
52
|
+
"new": "--<role>-subtitle",
|
|
53
|
+
"action": "Rename the suffix on all eight: `--border-subtle`, `--error-subtle`, `--info-subtle`, `--primary-subtle`, `--secondary-subtle`, `--success-subtle`, `--tertiary-subtle`, `--warning-subtle` each become `--<role>-subtitle`. A plain search-and-replace of `-subtle` to `-subtitle` inside a custom-property name does the whole set.",
|
|
54
|
+
"appliesWhen": "Only a stylesheet or template of yours that reads one of the eight by name. A consumer who never overrode a subtle token has nothing to do.",
|
|
55
|
+
"pitfall": "The old names do not error and do not warn — a `var(--primary-subtle)` that no longer resolves falls back to nothing, so the element loses its tint and keeps rendering. Only looking at the screen finds it.",
|
|
56
|
+
"note": "Eight semantic tint tokens changed suffix: the `-subtle` family became `-subtitle` across border, error, info, primary, secondary, success, tertiary and warning. There is no `--surface-subtle` in this library and there never was.",
|
|
54
57
|
"searchHints": [
|
|
55
|
-
"
|
|
58
|
+
"-subtle",
|
|
59
|
+
"--border-subtle",
|
|
60
|
+
"--error-subtle",
|
|
61
|
+
"--info-subtle",
|
|
62
|
+
"--primary-subtle",
|
|
63
|
+
"--secondary-subtle",
|
|
64
|
+
"--success-subtle",
|
|
65
|
+
"--tertiary-subtle",
|
|
66
|
+
"--warning-subtle"
|
|
56
67
|
],
|
|
57
|
-
"surface": "style"
|
|
68
|
+
"surface": "style",
|
|
69
|
+
"verify": "No stylesheet of yours reads a `--*-subtle` custom property any more, and every tint that was styled through one still paints."
|
|
58
70
|
},
|
|
59
71
|
{
|
|
60
72
|
"id": "success-subtle-token-rename",
|
package/migrations/0.2.2.json
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"items": [],
|
|
4
4
|
"informational": [
|
|
5
5
|
"New .t-mono-inline typography utility (inline code chip), completing the mono family alongside .t-mono and .t-mono-block — additive.",
|
|
6
|
-
"npm package hygiene: repository field dropped from package.json,
|
|
6
|
+
"npm package hygiene: repository field dropped from package.json, README license entry made plain text (fixes the npm 404). No consumer action."
|
|
7
7
|
],
|
|
8
8
|
"deleteList": []
|
|
9
9
|
}
|
package/migrations/0.3.0.json
CHANGED
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
"kind": "behavior",
|
|
26
26
|
"old": "--ds-*-fg",
|
|
27
27
|
"new": null,
|
|
28
|
-
"action": "For each `-fg` token you override, look the replacement up in the
|
|
28
|
+
"action": "For each `-fg` token you override, look the replacement up in the 0.3.0 token reference on the documentation site, which lists every `--ds-*`; the global roles are also readable in the installed package under `themes/` and `styles/`. Three suffixes are in play and the split is real: at 0.3.0 the package carries 23 `-text-color`, 49 `-label-color` and 21 `-icon-color`.",
|
|
29
29
|
"appliesWhen": "Only to DS-owned tokens. A variable of your own ending in `-fg` is untouched.",
|
|
30
30
|
"pitfall": "The suffix is NOT derivable from the old name, so guessing produces a name nothing reads and a silently unstyled element. Same shape, three answers: `--ds-modal-title-fg` became `-text-color`, `--ds-sidenav-group-fg` became `-label-color`, `--ds-icon-button-fg` became `-icon-color`.",
|
|
31
31
|
"note": "The `fg` abbreviation was dropped for a suffix that says what the token paints — text, a control or nav label, or a glyph. It covers the public `--ds-<component>-…-fg` hooks on avatar, badge, banner, breadcrumbs, button, date-picker, dropzone, empty-state, icon-button, input, menu, modal, page-header, pagination, search, sidenav, table, tabs, tag and topbar, plus the `--status-*` and chart-tooltip globals.",
|
package/migrations/0.4.0.json
CHANGED
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
"warning": "color=\"warning\"",
|
|
26
26
|
"text": "variant=\"text\""
|
|
27
27
|
},
|
|
28
|
-
"surface": "template",
|
|
28
|
+
"surface": ["template", "style", "typescript"],
|
|
29
29
|
"verify": "No ds-button carries a variant value outside the shipped set, and every button that used to name a colour through `variant` now names it through the colour input. Buttons render in the colour they did before the upgrade, not all in the default."
|
|
30
30
|
},
|
|
31
31
|
{
|
|
@@ -27,9 +27,7 @@ There are three moving parts:
|
|
|
27
27
|
`[data-status='…']` rules that set the public component tokens:
|
|
28
28
|
|
|
29
29
|
```scss
|
|
30
|
-
// external consumer of the published package:
|
|
31
30
|
@use '@ids-group-ltd/ids-design-system/styles/status' as status;
|
|
32
|
-
// inside this repo (ds-docs, loadPaths: src/lib): @use 'styles/status' as status;
|
|
33
31
|
|
|
34
32
|
@include status.define(
|
|
35
33
|
(
|
|
@@ -178,4 +176,4 @@ ds-badge.chip.in-transit { … } // .chip now carries layout rules only
|
|
|
178
176
|
```
|
|
179
177
|
|
|
180
178
|
This unifies every badge on one mechanism and restores the values that used to rely on factory
|
|
181
|
-
colours.
|
|
179
|
+
colours.
|
package/migrations/0.5.1.json
CHANGED
|
@@ -84,7 +84,7 @@
|
|
|
84
84
|
"style",
|
|
85
85
|
"typescript"
|
|
86
86
|
],
|
|
87
|
-
"verify": "No `variant`
|
|
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."
|
|
88
88
|
},
|
|
89
89
|
{
|
|
90
90
|
"id": "modal-confirm-tone-danger-remap",
|
package/migrations/0.6.3.json
CHANGED
|
@@ -41,7 +41,7 @@
|
|
|
41
41
|
"kind": "behavior",
|
|
42
42
|
"old": null,
|
|
43
43
|
"new": null,
|
|
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.
|
|
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
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
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
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.",
|
package/migrations/0.7.1.json
CHANGED
|
@@ -3,12 +3,12 @@
|
|
|
3
3
|
"items": [
|
|
4
4
|
{
|
|
5
5
|
"id": "surface-motion-partial-a-la-carte",
|
|
6
|
-
"kind": "
|
|
7
|
-
"old":
|
|
8
|
-
"new": "@use '@ids-group-ltd/ids-design-system/styles/surface-motion'
|
|
6
|
+
"kind": "code-add",
|
|
7
|
+
"old": null,
|
|
8
|
+
"new": "@use '@ids-group-ltd/ids-design-system/styles/surface-motion';",
|
|
9
9
|
"action": "Add `@use '@ids-group-ltd/ids-design-system/styles/surface-motion';` to your styles entry, beside `styles/overlay-motion`. If you have no overlay-motion line, put it beside whatever DS partials you do `@use`. Order does not matter.",
|
|
10
10
|
"appliesWhen": "Only à-la-carte consumers who `@use` DS partials individually. `styles/ds` forwards it, so its users need nothing at all.",
|
|
11
|
-
"pitfall": "Missing it fails SILENTLY — no error, no warning. The keyframes simply do not exist, and modal, drawer, bottom-sheet, toast, banner, alert, loading-overlay and the overlay panels all render with no entrance animation. Write the package-qualified specifier too: a bare `styles/…`
|
|
11
|
+
"pitfall": "Missing it fails SILENTLY — no error, no warning. The keyframes simply do not exist, and modal, drawer, bottom-sheet, toast, banner, alert, loading-overlay and the overlay panels all render with no entrance animation. Write the package-qualified specifier too: a bare `styles/…` does not resolve in a consumer build.",
|
|
12
12
|
"note": "A new global partial `styles/_surface-motion.scss` holds the shared entrance keyframes — ds-fade-in, ds-scale-in, ds-slide-in, ds-slide-edge-in — that every DS surface names through `--ds-<surface>-enter-keyframes`.",
|
|
13
13
|
"searchHints": [
|
|
14
14
|
"styles/overlay-motion",
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
"new": null,
|
|
26
26
|
"action": "Gate on `sortDir`, not on `sortKey`. `if (sortKey())` becomes `if (sortDir())`, and a server query built as `orderBy: sortKey()` must skip the clause when `sortDir()` is null.",
|
|
27
27
|
"appliesWhen": "Hosts that already read both need nothing, and neither do those passing `sortingOrder: ['asc','desc']`, which has no unsorted state. The table's own icons, aria-sort and client-side sorting were always gated on `sortDir` and are unchanged.",
|
|
28
|
-
"pitfall": "This item finds NOTHING in a template. The code that breaks is the host's own — a store, a page class, a query builder — and it names no DS symbol at all, so a search for `ds-table` comes back clean and the item gets recorded not-applicable.
|
|
28
|
+
"pitfall": "This item finds NOTHING in a template. The code that breaks is the host's own — a store, a page class, a query builder — and it names no DS symbol at all, so a search for `ds-table` comes back clean and the item gets recorded not-applicable. A common shape is `sorting: store.sortKey() ? { path: store.sortKey()!, order: store.sortDir() ?? 'Asc' } : undefined`, which keeps ordering a server-paged list by the last column the reader touched while the header shows no sort. Grep the `.ts` for the `detect` shapes.",
|
|
29
29
|
"note": "`sortKey` is no longer nulled when the cycle reaches unsorted: it keeps naming the column the user last touched, and `sortDir === null` alone means unsorted. It fixes a header desync for hosts that map \"off\" back to their own default sort.",
|
|
30
30
|
"searchHints": [
|
|
31
31
|
"sortKey",
|
|
@@ -231,7 +231,7 @@
|
|
|
231
231
|
"find": [
|
|
232
232
|
"[reserveMessage]=\"false\""
|
|
233
233
|
],
|
|
234
|
-
"why": "The default is FALSE again, so an opt-out binding only restates it - unless the field sits under a `dsReserveMessages` host or an app config that turns it on, where the binding is still the way back out.
|
|
234
|
+
"why": "The default is FALSE again, so an opt-out binding only restates it - unless the field sits under a `dsReserveMessages` host or an app config that turns it on, where the binding is still the way back out.",
|
|
235
235
|
"replaceWith": "nothing - delete the binding where no host reserves"
|
|
236
236
|
},
|
|
237
237
|
{
|