@ids-group-ltd/ids-design-system 0.11.1 → 0.11.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +342 -31
- package/components.md +27 -12
- package/design-system.md +135 -1
- package/docs/agent/INDEX.md +98 -0
- package/docs/agent/domain/ds-w3w.md +10 -0
- package/docs/agent/feedback/ds-alert.md +9 -0
- package/docs/agent/feedback/ds-avatar-group.md +7 -0
- package/docs/agent/feedback/ds-avatar.md +6 -0
- package/docs/agent/feedback/ds-badge.md +7 -0
- package/docs/agent/feedback/ds-banner.md +10 -0
- package/docs/agent/feedback/ds-empty-state.md +7 -0
- package/docs/agent/feedback/ds-progress.md +7 -0
- package/docs/agent/feedback/ds-skeleton.md +6 -0
- package/docs/agent/feedback/ds-spinner.md +6 -0
- package/docs/agent/feedback/ds-stat.md +7 -0
- package/docs/agent/feedback/ds-status-dot.md +6 -0
- package/docs/agent/feedback/ds-tag.md +8 -0
- package/docs/agent/feedback/ds-toast.md +12 -0
- package/docs/agent/forms/ds-autocomplete.md +9 -0
- package/docs/agent/forms/ds-button.md +14 -0
- package/docs/agent/forms/ds-checkbox.md +6 -0
- package/docs/agent/forms/ds-date-picker.md +7 -0
- package/docs/agent/forms/ds-dropzone.md +10 -0
- package/docs/agent/forms/ds-icon-button.md +10 -0
- package/docs/agent/forms/ds-input.md +22 -0
- package/docs/agent/forms/ds-multi-select.md +6 -0
- package/docs/agent/forms/ds-number-stepper.md +8 -0
- package/docs/agent/forms/ds-radio.md +6 -0
- package/docs/agent/forms/ds-search.md +10 -0
- package/docs/agent/forms/ds-select.md +7 -0
- package/docs/agent/forms/ds-switch.md +6 -0
- package/docs/agent/forms/ds-textarea.md +9 -0
- package/docs/agent/forms/the-picker-family-ds-select-ds-multi-select-ds-autocomplete.md +21 -0
- package/docs/agent/foundations/global-helper-classes.md +18 -0
- package/docs/agent/foundations/grid.md +35 -0
- package/docs/agent/foundations/tokens.md +47 -0
- package/docs/agent/navigation/ds-app-layout.md +10 -0
- package/docs/agent/navigation/ds-auth-layout.md +9 -0
- package/docs/agent/navigation/ds-breadcrumbs.md +7 -0
- package/docs/agent/navigation/ds-divider.md +9 -0
- package/docs/agent/navigation/ds-page-footer.md +7 -0
- package/docs/agent/navigation/ds-page-header.md +8 -0
- package/docs/agent/navigation/ds-pagination.md +7 -0
- package/docs/agent/navigation/ds-sidenav-group.md +8 -0
- package/docs/agent/navigation/ds-sidenav-item.md +9 -0
- package/docs/agent/navigation/ds-sidenav.md +9 -0
- package/docs/agent/navigation/ds-stepper.md +6 -0
- package/docs/agent/navigation/ds-tabs.md +9 -0
- package/docs/agent/navigation/ds-topbar.md +8 -0
- package/docs/agent/overlays/ds-bottom-sheet.md +9 -0
- package/docs/agent/overlays/ds-drawer.md +9 -0
- package/docs/agent/overlays/ds-menu.md +8 -0
- package/docs/agent/overlays/ds-modal-card.md +6 -0
- package/docs/agent/overlays/ds-modal.md +8 -0
- package/docs/agent/overlays/ds-popover.md +6 -0
- package/docs/agent/overlays/ds-tooltip.md +8 -0
- package/docs/agent/platform/breadcrumbs-service.md +30 -0
- package/docs/agent/platform/ds-config.md +60 -0
- package/docs/agent/platform/ds-icon-registry.md +23 -0
- package/docs/agent/platform/toast-service.md +19 -0
- package/docs/agent/surfaces/ds-accordion.md +8 -0
- package/docs/agent/surfaces/ds-card.md +10 -0
- package/docs/agent/tables/ds-table.md +15 -0
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +1530 -865
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.11.0.json +0 -45
- package/migrations/0.11.1.json +9 -35
- package/migrations/0.11.2.json +158 -0
- package/migrations/0.11.3.json +152 -0
- package/migrations/0.2.0.json +17 -5
- package/migrations/0.4.0.json +1 -1
- package/migrations/0.7.1.json +3 -3
- package/migrations/0.9.0.json +2 -2
- package/package.json +1 -1
- package/styles/_dropdown-overlay.scss +50 -38
- package/styles/_ds-color.scss +31 -12
- package/styles/_tokens-charts.scss +2 -3
- package/styles/_tokens.scss +159 -322
- package/themes/README.md +35 -4
- package/themes/_base-palette.scss +35 -76
- package/themes/_semantic.scss +5 -2
- package/types/ids-group-ltd-ids-design-system.d.ts +424 -188
package/migrations/0.11.0.json
CHANGED
|
@@ -71,51 +71,6 @@
|
|
|
71
71
|
"--ds-menu-divider-spacing"
|
|
72
72
|
]
|
|
73
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
74
|
{
|
|
120
75
|
"id": "sidenav-item-without-destination-is-a-button",
|
|
121
76
|
"kind": "behavior",
|
package/migrations/0.11.1.json
CHANGED
|
@@ -67,11 +67,18 @@
|
|
|
67
67
|
"old": "class MySelect extends SelectComponent, class MyMultiSelect extends MultiSelectComponent, class MyAutocomplete extends AutocompleteComponent",
|
|
68
68
|
"new": null,
|
|
69
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.",
|
|
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
71
|
"searchHints": [
|
|
72
72
|
"extends SelectComponent",
|
|
73
73
|
"extends MultiSelectComponent",
|
|
74
|
-
"extends AutocompleteComponent"
|
|
74
|
+
"extends AutocompleteComponent",
|
|
75
|
+
"DsControlWidth",
|
|
76
|
+
"DsTriggerDisplay",
|
|
77
|
+
"DsChipTemplateDirective",
|
|
78
|
+
"DsCreateTemplateDirective",
|
|
79
|
+
"DsEmptyTemplateDirective",
|
|
80
|
+
"DsOptionTemplateDirective",
|
|
81
|
+
"DsPickerTriggerDirective"
|
|
75
82
|
],
|
|
76
83
|
"surface": "typescript",
|
|
77
84
|
"detect": [
|
|
@@ -167,39 +174,6 @@
|
|
|
167
174
|
"verify": "The trigger still shows a caption and a count badge.",
|
|
168
175
|
"restore": null
|
|
169
176
|
},
|
|
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
177
|
{
|
|
204
178
|
"id": "autocomplete-options-element-type-widened",
|
|
205
179
|
"kind": "behavior",
|
|
@@ -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
|
+
}
|
|
@@ -0,0 +1,152 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.11.3",
|
|
3
|
+
"items": [
|
|
4
|
+
{
|
|
5
|
+
"id": "banner-icon-top-offset-token-removed",
|
|
6
|
+
"kind": "removed-api",
|
|
7
|
+
"old": "--banner-ic-mt",
|
|
8
|
+
"new": null,
|
|
9
|
+
"appliesWhen": "You set --banner-ic-mt anywhere. It is a global geometry token, not a --ds-* component hook, so an app that only overrides --ds-banner-* is unaffected.",
|
|
10
|
+
"pitfall": "Deleting the override is the whole fix, but only because the icon no longer needs nudging: it is now centred on the message block rather than aligned to the first line. If you had raised the value to line the icon up with a taller first line, that adjustment is now working against the new rule and will push the icon off centre.",
|
|
11
|
+
"searchHints": [
|
|
12
|
+
"banner-ic-mt"
|
|
13
|
+
],
|
|
14
|
+
"surface": "style",
|
|
15
|
+
"detect": [
|
|
16
|
+
"--banner-ic-mt"
|
|
17
|
+
],
|
|
18
|
+
"verify": "A ds-banner with two or more lines of body text shows its icon vertically centred on the text block, and no rule in your app references --banner-ic-mt.",
|
|
19
|
+
"restore": "There is no one-line restore. `align-self: flex-start` on the icon does not reproduce the old look: it drops the one border-width of nudge the token supplied on a banner (the toast never read it — its own 2px came from a margin, removed with the same change), and a consumer's `ds-banner .icon` is specificity (0,1,1) against the component's own (0,4,0), so it does not win at all. On a `compact` banner it is actively wrong, because that variant was already centred before this change. If you must have the old alignment, fork the component's stylesheet.",
|
|
20
|
+
"note": "The token was one border-width of optical bump, and it existed only to serve the first-line alignment rule. With the icon centred on the block there is nothing left for it to correct.",
|
|
21
|
+
"action": "Delete any --banner-ic-mt declaration. There is no replacement token."
|
|
22
|
+
},
|
|
23
|
+
{
|
|
24
|
+
"id": "toast-region-subclass-members-moved",
|
|
25
|
+
"kind": "behavior",
|
|
26
|
+
"old": "class MyToastRegion extends ToastRegionComponent",
|
|
27
|
+
"new": null,
|
|
28
|
+
"action": "Build after upgrading. Rename or mark `override` every member the compiler reports as colliding, and DELETE any `override startCountdown` - that member no longer exists, so the override is dead code the compiler will not complain about.",
|
|
29
|
+
"appliesWhen": "Only a class that extends ToastRegionComponent. Template users of `<ds-toast-region>` and callers of ToastService need nothing.",
|
|
30
|
+
"pitfall": "`startCountdown` was announced in 0.11.2 as a member the region had just GAINED, so an override written for that release is one release old and now overrides nothing: it compiles clean and silently never runs. And every one of the five new names is `private` or `protected`, which is no protection - a redeclared private fails with TS2415 exactly as a public collision does.",
|
|
31
|
+
"note": "ToastRegionComponent gained `arm`, `pauseAll`, `remaining`, `resumeAll` and `startedAt`, and lost `startCountdown`. A countdown is armed when a toast is promoted to visible, and re-armed from what is left when a hover or focus pause ends - the region owns the timing because only it knows when a toast became visible. None of the five is public API or a signal, and there is no public replacement for `startCountdown`.",
|
|
32
|
+
"searchHints": [
|
|
33
|
+
"extends ToastRegionComponent",
|
|
34
|
+
"ToastRegionComponent",
|
|
35
|
+
"startCountdown",
|
|
36
|
+
"override startCountdown",
|
|
37
|
+
"pauseAll",
|
|
38
|
+
"resumeAll",
|
|
39
|
+
"TS2415",
|
|
40
|
+
"TS4114"
|
|
41
|
+
],
|
|
42
|
+
"surface": "typescript",
|
|
43
|
+
"detect": [
|
|
44
|
+
"extends ToastRegionComponent",
|
|
45
|
+
"override startCountdown"
|
|
46
|
+
],
|
|
47
|
+
"verify": "The app builds with no TS4114 / TS2415 / TS2416 naming ToastRegionComponent, and no `override startCountdown` remains in your source.",
|
|
48
|
+
"restore": null
|
|
49
|
+
},
|
|
50
|
+
{
|
|
51
|
+
"id": "banner-dismissed-output-never-existed",
|
|
52
|
+
"kind": "output-rename",
|
|
53
|
+
"old": "ds-banner[dismissed]",
|
|
54
|
+
"new": "closed",
|
|
55
|
+
"action": "On every `<ds-banner>`, rename the binding `(dismissed)` to `(closed)`.",
|
|
56
|
+
"appliesWhen": "Only if you bound `(dismissed)` on a `<ds-banner>`. It was never an output of this component, so the handler has never run.",
|
|
57
|
+
"pitfall": "Nothing errors and nothing logs: an unknown event binding registers a DOM listener for an event no one dispatches, so `(dismissed)` looks wired and is inert. Only checking that the handler runs finds it.",
|
|
58
|
+
"note": "`ds-banner` emits `(closed)`. `(dismissed)` was published in the component catalogue and is not an output of the class.",
|
|
59
|
+
"searchHints": [
|
|
60
|
+
"(dismissed)",
|
|
61
|
+
"<ds-banner",
|
|
62
|
+
"(closed)"
|
|
63
|
+
],
|
|
64
|
+
"surface": "template",
|
|
65
|
+
"verify": "Every `<ds-banner>` handler you expected to run does run — bind it and confirm the callback fires."
|
|
66
|
+
},
|
|
67
|
+
{
|
|
68
|
+
"id": "toast-dismissed-output-never-existed",
|
|
69
|
+
"kind": "output-rename",
|
|
70
|
+
"old": "ds-toast[dismissed]",
|
|
71
|
+
"new": "closed",
|
|
72
|
+
"action": "On every `<ds-toast>`, rename the binding `(dismissed)` to `(closed)`.",
|
|
73
|
+
"appliesWhen": "Only if you bound `(dismissed)` on a `<ds-toast>`. It was never an output of this component, so the handler has never run.",
|
|
74
|
+
"pitfall": "Nothing errors and nothing logs: an unknown event binding registers a DOM listener for an event no one dispatches, so `(dismissed)` looks wired and is inert. Only checking that the handler runs finds it.",
|
|
75
|
+
"note": "`ds-toast` emits `(closed)`. `(dismissed)` was published in the component catalogue and is not an output of the class.",
|
|
76
|
+
"searchHints": [
|
|
77
|
+
"(dismissed)",
|
|
78
|
+
"<ds-toast",
|
|
79
|
+
"(closed)"
|
|
80
|
+
],
|
|
81
|
+
"surface": "template",
|
|
82
|
+
"verify": "Every `<ds-toast>` handler you expected to run does run — bind it and confirm the callback fires."
|
|
83
|
+
},
|
|
84
|
+
{
|
|
85
|
+
"id": "pagination-page-change-output-never-existed",
|
|
86
|
+
"kind": "output-rename",
|
|
87
|
+
"old": "ds-pagination[pageChange]",
|
|
88
|
+
"new": "currentPageChange",
|
|
89
|
+
"action": "On every `<ds-pagination>`, rename the binding `(pageChange)` to `(currentPageChange)`.",
|
|
90
|
+
"appliesWhen": "Only if you bound `(pageChange)` on a `<ds-pagination>`. It was never an output of this component, so the handler has never run.",
|
|
91
|
+
"pitfall": "Nothing errors and nothing logs: an unknown event binding registers a DOM listener for an event no one dispatches, so `(pageChange)` looks wired and is inert. Only checking that the handler runs finds it.",
|
|
92
|
+
"note": "`ds-pagination` emits `(currentPageChange)`. `(pageChange)` was published in the component catalogue and is not an output of the class.",
|
|
93
|
+
"searchHints": [
|
|
94
|
+
"(pageChange)",
|
|
95
|
+
"<ds-pagination",
|
|
96
|
+
"(currentPageChange)"
|
|
97
|
+
],
|
|
98
|
+
"surface": "template",
|
|
99
|
+
"verify": "Every `<ds-pagination>` handler you expected to run does run — bind it and confirm the callback fires."
|
|
100
|
+
},
|
|
101
|
+
{
|
|
102
|
+
"id": "table-row-click-output-never-existed",
|
|
103
|
+
"kind": "output-rename",
|
|
104
|
+
"old": "ds-table[rowClick]",
|
|
105
|
+
"new": "rowClicked",
|
|
106
|
+
"action": "On every `<ds-table>`, rename the binding `(rowClick)` to `(rowClicked)`.",
|
|
107
|
+
"appliesWhen": "Only if you bound `(rowClick)` on a `<ds-table>`. It was never an output of this component, so the handler has never run.",
|
|
108
|
+
"pitfall": "Nothing errors and nothing logs: an unknown event binding registers a DOM listener for an event no one dispatches, so `(rowClick)` looks wired and is inert. Only checking that the handler runs finds it.",
|
|
109
|
+
"note": "`ds-table` emits `(rowClicked)`. `(rowClick)` was published in the component catalogue and is not an output of the class.",
|
|
110
|
+
"searchHints": [
|
|
111
|
+
"(rowClick)",
|
|
112
|
+
"<ds-table",
|
|
113
|
+
"(rowClicked)"
|
|
114
|
+
],
|
|
115
|
+
"surface": "template",
|
|
116
|
+
"verify": "Every `<ds-table>` handler you expected to run does run — bind it and confirm the callback fires."
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": "ds-color-mixin-rejects-unknown-family",
|
|
120
|
+
"kind": "behavior",
|
|
121
|
+
"old": "ds.color(",
|
|
122
|
+
"new": null,
|
|
123
|
+
"action": "Change every `@include ds.color(<name>)` to one of `secondary`, `tertiary`, `error`, `success` or `warning`, or delete the include if the zone was never painting.",
|
|
124
|
+
"appliesWhen": "Only a consumer whose own Sass calls the mixin. The `ds-color=\"…\"` attribute in a template runs no Sass and is unaffected.",
|
|
125
|
+
"pitfall": "This is a hard build failure, not a warning — the `@error` aborts the compile, so a wrong name that used to ship silently now stops the build. That is the point: the eleven pointers it emitted could never resolve, so the zone painted with `unset` and read as a theming problem.",
|
|
126
|
+
"note": "`ds.color($family)` validates its argument against the five families it supports. It previously accepted any name and emitted pointers at guaranteed-invalid values.",
|
|
127
|
+
"searchHints": [
|
|
128
|
+
"ds.color(",
|
|
129
|
+
"@include ds.color",
|
|
130
|
+
"styles/ds-color"
|
|
131
|
+
],
|
|
132
|
+
"surface": "style",
|
|
133
|
+
"verify": "Your Sass compiles, and every `ds-color` zone shows its family's accent rather than falling back to the default.",
|
|
134
|
+
"restore": null,
|
|
135
|
+
"detect": [
|
|
136
|
+
"ds.color(",
|
|
137
|
+
"@include ds.color"
|
|
138
|
+
]
|
|
139
|
+
}
|
|
140
|
+
],
|
|
141
|
+
"informational": [
|
|
142
|
+
"The banner, toast and alert icon now centres on the message block instead of aligning to the first line of text. Nothing to change: it is a visual default, applied by the components themselves. One-line messages look identical either way, which covers most toasts; the difference grows with the text, and was 12px at two lines and 21px at three.",
|
|
143
|
+
"ToastService.promise() and any toast with an `action` changed their dismissal timing. A settled promise toast now counts its 4s/6s from when it becomes visible rather than from when the promise resolved, so one queued behind `maxVisible` is no longer removed before it is shown. A toast with an `action` no longer auto-dismisses at all and is always dismissible, because the region is last in tab order and the button was unreachable within the old five seconds. Hovering or focusing the region pauses every countdown. Nothing to change in consumer code; if you relied on an action toast disappearing on its own, dismiss it from the action handler.",
|
|
144
|
+
"Inside a `ds-color=\"error\"`, `=\"success\"` or `=\"warning\"` zone, anything that reads the scoped accent's strong colour now renders in that status colour instead of falling back to body text — selected list and tree rows, the active sidenav item and its rail, the active tab pill, avatar initials, the active tag, dropzone text and the toast's action label. Nothing to change: those three families simply never defined the role the zone asked for, and the pointer now asks for the name they do define. A zone whose accent looked plain before will now look coloured, which is the intended appearance.",
|
|
145
|
+
"ds-banner's close button gained aria-label=\"Dismiss\", which ds-toast and ds-alert already carried. NO ACTION.",
|
|
146
|
+
"A toast body now wraps an unbroken token instead of overflowing the pill. NO ACTION.",
|
|
147
|
+
"The toast region's hover/focus pause is derived from both sources rather than latched, so tabbing out of a region the pointer still covers does not resume, focus moving inside it is not a leave, and a toast that becomes visible while paused is banked rather than counted. A resumed toast always gets at least 600ms. NO ACTION.",
|
|
148
|
+
"ds-config and the card types moved inside the library. Every symbol still reaches the package root unchanged, and no import path of yours could have named the old location: there is one entry point and no subpath resolves into lib/. NO ACTION.",
|
|
149
|
+
"A disabled ds-accordion-item's chevron asked for a colour token this library does not define, so the declaration was invalid and the chevron inherited the surrounding colour while its label greyed correctly. It reads the disabled text colour now. NO ACTION."
|
|
150
|
+
],
|
|
151
|
+
"deleteList": []
|
|
152
|
+
}
|
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.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
|
{
|
package/migrations/0.7.1.json
CHANGED
|
@@ -3,9 +3,9 @@
|
|
|
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
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.",
|
package/migrations/0.9.0.json
CHANGED
|
@@ -194,8 +194,8 @@
|
|
|
194
194
|
"new": null,
|
|
195
195
|
"action": "Build after upgrading: the compiler raises most of these collisions, but NOT the ones named in `pitfall` below — check those by hand, because they compile clean. Then per member: rename your own, or add `override` where the base semantics genuinely match.",
|
|
196
196
|
"appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users need nothing.",
|
|
197
|
-
"pitfall": "Two things the compiler will NOT tell you. `isStriped()` keeps its signature but now takes an ABSOLUTE row index rather than a window-relative one, so a subclass that overrode it silently computes the wrong row. And `distinctValuesOf()` was replaced by `optionsFor()` — a subclass that CALLED the old name loses it silently at the call site while only the declaration errors. Also note both CVA bases gained a `focus()` inherited by every field control, so a subclass with its own needs `override`, and
|
|
198
|
-
"note": "TableComponent changed by far the most; ModalComponent, ModalCardComponent, InputComponent, TextareaComponent, SelectComponent, AutocompleteComponent, BreadcrumbsComponent, MenuItemComponent,
|
|
197
|
+
"pitfall": "Two things the compiler will NOT tell you. `isStriped()` keeps its signature but now takes an ABSOLUTE row index rather than a window-relative one, so a subclass that overrode it silently computes the wrong row. And `distinctValuesOf()` was replaced by `optionsFor()` — a subclass that CALLED the old name loses it silently at the call site while only the declaration errors. Also note both CVA bases gained a `focus()` inherited by every field control, so a subclass with its own needs `override`, and five new exported symbols can shadow a local name: AuthLayoutComponent, FieldGroupComponent, DS_FIELD_GROUP, HeaderFilterDirective, HeaderFilterContext — none of these existed at 0.8.0, so they are new exports rather than grown classes.",
|
|
198
|
+
"note": "Seventeen classes grew a member. TableComponent changed by far the most; ModalComponent, ModalCardComponent, InputComponent, TextareaComponent, SelectComponent, AutocompleteComponent, BreadcrumbsComponent, MenuItemComponent, ButtonComponent, DatePickerComponent, SearchComponent (the last three gained `inGroup`), AppLayoutComponent, TabsComponent, LayoutScrollService and both CVA bases also moved. TS4114 demands `override`, TS2415 fires on a redeclared private, TS2416 on a differing signature.",
|
|
199
199
|
"searchHints": [
|
|
200
200
|
"extends TableComponent",
|
|
201
201
|
"extends InputComponent",
|
package/package.json
CHANGED