@ids-group-ltd/ids-design-system 0.10.0 → 0.10.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 +622 -12
- package/components.md +68 -13
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +748 -702
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.10.0.json +420 -44
- package/migrations/0.10.1.json +223 -0
- package/migrations/0.10.2.json +482 -0
- package/migrations/0.2.0.json +32 -8
- package/migrations/0.3.0.json +19 -3
- package/migrations/0.4.0.json +50 -11
- package/migrations/0.5.0.json +93 -24
- package/migrations/0.5.1.json +106 -29
- package/migrations/0.6.0.json +2 -1
- package/migrations/0.6.2.json +33 -3
- package/migrations/0.6.3.json +19 -3
- package/migrations/0.7.0.json +77 -25
- package/migrations/0.7.1.json +84 -8
- package/migrations/0.8.0.json +46 -10
- package/migrations/0.9.0.json +284 -35
- package/migrations/AUTHORING.md +125 -12
- package/migrations/README.md +62 -5
- package/package.json +1 -1
- package/styles/_dropdown-overlay.scss +4 -3
- package/styles/_field-group-segment.scss +9 -0
- package/styles/_focus.scss +16 -0
- package/styles/_text-clip.scss +17 -0
- package/styles/_tokens.scss +0 -2
- package/themes/_semantic.scss +20 -3
- package/types/ids-group-ltd-ids-design-system.d.ts +296 -402
|
@@ -0,0 +1,223 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.10.1",
|
|
3
|
+
"items": [
|
|
4
|
+
{
|
|
5
|
+
"id": "opacity-muted-token-removed",
|
|
6
|
+
"kind": "removed-api",
|
|
7
|
+
"old": "--opacity-muted",
|
|
8
|
+
"new": null,
|
|
9
|
+
"note": "The --opacity-muted custom property (0.6) is deleted from the token scale. No component has read it since 0.10.0 moved the disabled states onto --text-disabled + --opacity-disabled, so REMOVING IT CHANGES NOTHING THE LIBRARY RENDERS. Two consumer cases. (1) You SET it - most likely on ds-button or ds-icon-button, the override 0.10.0's DELETE-LIST already warned about: delete the declaration, it was a no-op then and is a no-op now (those two resolve their disabled state from oklch(from accent ...) colours, and --ds-button-label-color-disabled / --ds-icon-button-icon-color-disabled are the real hooks). (2) You READ it in your own CSS, i.e. var(--opacity-muted) appears in a value you wrote: that now resolves to nothing and the declaration is dropped, so pick the token that names the job instead - --opacity-disabled (0.5) where opacity is the ONLY disabled signal, --opacity-text-disabled (0.38) for disabled text - or inline 0.6 if what you actually wanted was de-emphasis rather than a disabled state. Do not re-declare --opacity-muted yourself to keep it alive: 'muted' is a de-emphasis level and disabled is a state, and sharing one number between them is what put this token on the DELETE-LIST in the first place.",
|
|
10
|
+
"searchHints": [
|
|
11
|
+
"--opacity-muted",
|
|
12
|
+
"var(--opacity-muted",
|
|
13
|
+
"opacity-muted"
|
|
14
|
+
],
|
|
15
|
+
"surface": "style",
|
|
16
|
+
"verify": "No stylesheet declares or reads `--opacity-muted`: a declaration is a no-op and a read resolves to nothing, dropping the whole declaration."
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"id": "list-item-slots-outside-activator",
|
|
20
|
+
"kind": "behavior",
|
|
21
|
+
"old": "ds-list-item ::ng-deep .activator",
|
|
22
|
+
"new": null,
|
|
23
|
+
"note": "ds-list-item's DOM changed: `[leading]` and `[trailing]` are now siblings of `.activator` rather than children of it, so a row can hold a checkbox or a kebab alongside a row-level action. NO INPUT OR OUTPUT CHANGED -- title, subtitle, clickable, selected, disabled and activated all behave as before, and a plain row looks identical. WHAT MOVED: the row's `display: flex`, its `--ds-list-item-pad-*` padding, its `--ds-list-item-gap`, the hover tint and the selected tint all sit on the HOST now; `.activator` is just the text button and has no padding of its own. ACTION: a `::ng-deep .activator` override that set padding, gap, background or hover now applies to the text only -- move it to `ds-list-item` itself. Also fixed alongside: `selected` set `aria-current` on the inner button, so it was inert whenever `clickable` was false; it is on the host now, which means a non-clickable row marked selected is finally announced as current.",
|
|
24
|
+
"searchHints": [
|
|
25
|
+
"ds-list-item",
|
|
26
|
+
".activator",
|
|
27
|
+
"list-item-pad",
|
|
28
|
+
"list-item-gap",
|
|
29
|
+
"aria-current",
|
|
30
|
+
"leading",
|
|
31
|
+
"trailing",
|
|
32
|
+
"clickable"
|
|
33
|
+
],
|
|
34
|
+
"surface": "style",
|
|
35
|
+
"detect": [
|
|
36
|
+
"::ng-deep .activator",
|
|
37
|
+
".activator",
|
|
38
|
+
"ds-list-item"
|
|
39
|
+
],
|
|
40
|
+
"verify": "Any consumer rule that set padding, gap, background or a hover tint on ds-list-item's `.activator` now targets `ds-list-item` itself."
|
|
41
|
+
},
|
|
42
|
+
{
|
|
43
|
+
"id": "button-borderless-disabled-label-recipe",
|
|
44
|
+
"kind": "behavior",
|
|
45
|
+
"old": "ds-button[variant=\"ghost\"][disabled], ds-button[variant=\"text\"][disabled], ds-button[variant=\"outline\"][disabled]",
|
|
46
|
+
"new": null,
|
|
47
|
+
"note": "The DEFAULT disabled label colour changed for the three variants whose fill cannot carry the state. Was the shared `oklch(from <accent> 70% 0.035 h)`; is now `color-mix(in srgb, <label> 40%, var(--surface-default))` -- the lightness now moves toward the surface instead of being pinned at 70%. WHY: pinned at 70% the disabled label was two points of OKLCH lightness from the enabled one in the DARK theme (--primary-strong is L 67.9% there), a 1.11:1 gap, so a disabled ghost was indistinguishable from an active one. A fixed lightness cannot serve both themes -- in light disabled is lighter than the accent, in dark the accent is already light so disabled must go darker; only the surface knows that direction. Measured after: light 2.54 -> 3.41:1, dark 1.11 -> 2.91:1. `variant=\"outline\"` is included even though it has a border, because its DISABLED border resolves to only 1.30:1 against the page -- lower than its own enabled border at 1.49:1 -- so the label was carrying the state there too. NO ACTION NEEDED unless you relied on the exact old colour: `--ds-button-label-color-disabled` is the same hook and still wins, so an app that already sets it sees no change. If you matched the old #949EB5 by hand anywhere (a mock, a screenshot test, a hand-written CSS twin of the disabled state), for the default primary it is now #A5B4F8 in light and #3D4979 in dark. The label stays tinted rather than going grey -- chroma rises with the mix (0.036 -> 0.099 in light) -- which was chosen deliberately. LIMITATION: the mix target is --surface-default, a stand-in for the real backdrop, so a borderless button sitting on a tinted ground gets a label mixed against the page colour instead. `variant=\"solid\"` and `variant=\"tonal\"` are NOT affected and keep the shared recipe.",
|
|
48
|
+
"searchHints": [
|
|
49
|
+
"ds-button",
|
|
50
|
+
"variant=\"ghost\"",
|
|
51
|
+
"variant=\"text\"",
|
|
52
|
+
"variant=\"outline\"",
|
|
53
|
+
"--ds-button-label-color-disabled",
|
|
54
|
+
"label-color-disabled",
|
|
55
|
+
"#949EB5",
|
|
56
|
+
"disabled",
|
|
57
|
+
"oklch"
|
|
58
|
+
],
|
|
59
|
+
"surface": "style",
|
|
60
|
+
"restore": "--ds-button-label-color-disabled: #949EB5 (the old shared value; the hook still wins over the new default)",
|
|
61
|
+
"verify": "No hand-written twin of the disabled label colour - a mock, a screenshot baseline, a CSS copy - still names the old #949EB5."
|
|
62
|
+
},
|
|
63
|
+
{
|
|
64
|
+
"id": "icon-button-standard-disabled-icon-recipe",
|
|
65
|
+
"kind": "behavior",
|
|
66
|
+
"old": "ds-icon-button[variant=\"standard\"][disabled]",
|
|
67
|
+
"new": null,
|
|
68
|
+
"note": "The DEFAULT disabled glyph colour changed for variant=\"standard\" ONLY -- the one variant with no fill and no border, so the glyph colour is the whole signal. Was the shared `oklch(from <accent> 70% 0.035 h)`; is now `color-mix(in srgb, <icon colour> 40%, var(--surface-default))`. WHY: pinned at L 70% the disabled glyph sat only ten points of OKLCH lightness from the enabled one in the DARK theme (the enabled glyph is --text-secondary at L 80% there), a 1.46:1 gap. Light was already fine at 4.17:1 because the enabled glyph is L 35% there -- this is a dark-theme fix. Measured after: light 4.17 -> 5.19:1, dark 1.46 -> 3.58:1. NO ACTION NEEDED unless you relied on the exact old colour: `--ds-icon-button-icon-color-disabled` is the same hook and still wins. If you matched the old value by hand, for the default it was #969EB5 (light) / #949EB5 (dark) and is now #AEB1B8 (light) / #575D69 (dark). variant=\"filled\", \"tonal\" and \"outlined\" are NOT affected and keep the shared recipe -- filled deliberately so, because its glyph is --c-on (white) and mixing white into a white surface would not move it.",
|
|
69
|
+
"searchHints": [
|
|
70
|
+
"ds-icon-button",
|
|
71
|
+
"variant=\"standard\"",
|
|
72
|
+
"--ds-icon-button-icon-color-disabled",
|
|
73
|
+
"icon-color-disabled",
|
|
74
|
+
"#969EB5",
|
|
75
|
+
"disabled",
|
|
76
|
+
"oklch"
|
|
77
|
+
],
|
|
78
|
+
"surface": "style",
|
|
79
|
+
"restore": "--ds-icon-button-icon-color-disabled: #969EB5 (light) / #949EB5 (dark)",
|
|
80
|
+
"verify": "No hand-written copy of the disabled glyph colour still names the old #969EB5 / #949EB5."
|
|
81
|
+
},
|
|
82
|
+
{
|
|
83
|
+
"id": "fields-success-is-a-string",
|
|
84
|
+
"kind": "behavior",
|
|
85
|
+
"old": "ds-input [success]=\"true\"",
|
|
86
|
+
"new": null,
|
|
87
|
+
"note": "TWO changes in one, and only the first needs edits. (1) BREAKING on `ds-input`: `success` was `input(false, { transform: booleanAttribute })` and is now `input<string>('')`. A `[success]=\"true\"` binding now sets the literal text \"true\" as the message. Replace `[success]=\"true\" hint=\"Available\"` with `success=\"Available\"` -- the text moves out of `hint` and into `success`. A `[success]=\"someBoolean\"` binding must become `[success]=\"someBoolean ? 'Looks good' : ''\"`, since an empty string is now what means \"no success state\". (2) ADDITIVE: the same `success` input now also exists on ds-textarea, ds-select, ds-multi-select, ds-autocomplete, ds-date-picker, ds-time-picker, ds-otp-input and ds-color-picker, which had no success state at all. WHY THE TYPE CHANGED: `error` and `warning` already carried their own text, so `success` was the only state that could not say anything -- it was a flag that recoloured `hint` green, which meant the message had to be smuggled through a different input. It is now the fourth rung of the same ladder: error, errors, warning, success, hint. CONSEQUENCE: a success border with NO message is no longer expressible, exactly as it never was for `warning`. NOT added to ds-checkbox, ds-radio-group, ds-switch or ds-slider -- they have no bordered box, so the state would appear in the message line alone. `invalid` is unchanged and remains the flag partner of `error`. NOTE ON KIND: this is not a value remap even though it looks like one — there is no old value that maps to a new one, because the replacement TEXT did not exist before and has to be authored (usually by moving it out of `hint`).",
|
|
88
|
+
"searchHints": [
|
|
89
|
+
"success",
|
|
90
|
+
"[success]",
|
|
91
|
+
"ds-input",
|
|
92
|
+
"ds-textarea",
|
|
93
|
+
"ds-select",
|
|
94
|
+
"ds-date-picker",
|
|
95
|
+
"data-field-state",
|
|
96
|
+
"field-state",
|
|
97
|
+
"hint"
|
|
98
|
+
],
|
|
99
|
+
"surface": [
|
|
100
|
+
"template",
|
|
101
|
+
"typescript"
|
|
102
|
+
],
|
|
103
|
+
"detect": [
|
|
104
|
+
"[success]=\"true\"",
|
|
105
|
+
"[success]",
|
|
106
|
+
"success="
|
|
107
|
+
],
|
|
108
|
+
"verify": "No `[success]` binding passes a boolean: every one carries the message text, and an empty string is what means \"no success state\"."
|
|
109
|
+
},
|
|
110
|
+
{
|
|
111
|
+
"id": "fields-shared-base-class-members",
|
|
112
|
+
"kind": "behavior",
|
|
113
|
+
"old": "class MyField extends TextareaComponent (or any DS field)",
|
|
114
|
+
"new": null,
|
|
115
|
+
"note": "INTERNAL REFACTOR, no public API change -- listed only because it matters to SUBCLASSERS. The seven inputs every field shares (`hint`, `error`, `warning`, `errors`, `invalid`, `touched`, `reserveMessage`) plus the `reserveMessageResolved` helper are now declared once on a new `DsFieldBase` instead of being hand-copied into each of the fourteen fields. Every input keeps its name, type, default and documentation; the generated docs API reference was diffed and lost nothing. `DsControlValueAccessor` and `DsBooleanControlValueAccessor` now extend `DsFieldBase`, and `ds-radio` extends it directly. ACTION only if you SUBCLASS a DS field and declare a member with one of those seven names: it is now an inherited member rather than an own member, so an incompatible re-declaration fails to compile where it may previously have shadowed. Redeclaring with the same shape still works. `success`, `label`, `required` and `optional` were deliberately NOT lifted and remain per-component. SEPARATELY, a genuine new collision: `success` is a NEW member on the eight bordered fields that lacked it (ds-autocomplete, ds-color-picker, ds-date-picker, ds-multi-select, ds-otp-input, ds-select, ds-textarea, ds-time-picker), so a subclass of any of those declaring `success` now fails with TS4114. Beware the report itself here: `npm run class-surface` lists those seven moved names as LOST from fourteen field components, which is an artefact of counting declarations per FILE — they moved UP into DsFieldBase and every field still has them by inheritance. AUTHORING already flags a member that moved to a base class as something the tool cannot see.",
|
|
116
|
+
"searchHints": [
|
|
117
|
+
"extends TextareaComponent",
|
|
118
|
+
"extends InputComponent",
|
|
119
|
+
"DsFieldBase",
|
|
120
|
+
"DsControlValueAccessor",
|
|
121
|
+
"reserveMessage",
|
|
122
|
+
"reserveMessageResolved",
|
|
123
|
+
"touched"
|
|
124
|
+
],
|
|
125
|
+
"surface": "typescript",
|
|
126
|
+
"detect": [
|
|
127
|
+
"extends TextareaComponent",
|
|
128
|
+
"extends InputComponent",
|
|
129
|
+
"extends "
|
|
130
|
+
],
|
|
131
|
+
"verify": "A typecheck reports no TS4114 on a subclass of a DS field declaring hint, error, warning, errors, invalid, touched or reserveMessage - or `success` on one of the eight bordered fields that just gained it."
|
|
132
|
+
},
|
|
133
|
+
{
|
|
134
|
+
"id": "fields-invalid-no-longer-recolours-hint",
|
|
135
|
+
"kind": "behavior",
|
|
136
|
+
"old": "[invalid]=\"true\" hint=\"<message>\"",
|
|
137
|
+
"new": null,
|
|
138
|
+
"note": "BREAKING. `invalid` used to promote `hint` to the ERROR state -- a red message rendered through role=\"alert\". It now paints the control and sets aria-invalid only, and `hint` stays a neutral grey hint. ACTION: wherever a field binds `[invalid]` together with `hint` and expected the hint to read as the error, move the text to `error` and drop the `[invalid]` binding -- `error` implies the invalid state. So `[invalid]=\"true\" hint=\"Must be before end date\"` becomes `error=\"Must be before end date\"`. A dynamic form is `[error]=\"showError() ? 'Must be before end date' : ''\"`. WHY: the idiom lost the real hint (with both set, the help text was replaced rather than shown alongside), announced help text as an alert, and made a template unreadable because whether `hint` was a hint or an error depended on another attribute. It was the last input borrowing another's text. NO ACTION when `[invalid]` is used WITHOUT `hint` -- that is still supported and is exactly what the input is for: the error state with the message living elsewhere (a form-level error summary, one message for a whole ds-field-group), plus aria-invalid. `invalid` is not deprecated.",
|
|
139
|
+
"searchHints": [
|
|
140
|
+
"[invalid]",
|
|
141
|
+
"invalid",
|
|
142
|
+
"hint=",
|
|
143
|
+
"[hint]",
|
|
144
|
+
"error=",
|
|
145
|
+
"[error]",
|
|
146
|
+
"aria-invalid",
|
|
147
|
+
"role=\"alert\""
|
|
148
|
+
],
|
|
149
|
+
"surface": "template",
|
|
150
|
+
"detect": [
|
|
151
|
+
"[invalid]",
|
|
152
|
+
"hint="
|
|
153
|
+
],
|
|
154
|
+
"verify": "No field binds `[invalid]` together with `hint` expecting the hint to read as the error: that text sits on `error`, and `[invalid]` appears only where the message lives elsewhere (a form summary, a field group)."
|
|
155
|
+
},
|
|
156
|
+
{
|
|
157
|
+
"id": "fields-warning-kind-is-reserved",
|
|
158
|
+
"kind": "behavior",
|
|
159
|
+
"old": "a validator returning { warning: ... }",
|
|
160
|
+
"new": null,
|
|
161
|
+
"note": "The DsFieldError kind `warning` is now RESERVED, exported as DS_FIELD_WARNING_KIND. An error carrying it paints the field's warning state and shows its message, but leaves the control valid: aria-invalid stays off and a submit guard reading validity is not blocked. MOSTLY ADDITIVE -- it gives a form model a way to raise a non-blocking remark, which Angular's AbstractControl has no channel for. ACTION ONLY IF you already have a validator using the key `warning` (reactive/template-driven) or a signal-forms ValidationError with kind 'warning' for a BLOCKING error: it now reads as advisory, so the field stops being invalid and the submit stops being blocked. Rename that key to anything else -- e.g. `warningLimit`, `softLimit` -- and the old behaviour returns. Ranked below the explicit `warning` input, and shown only after interaction like any other validation message. DsFieldError and DsFieldErrorsInput are now exported as well, for writing a typed validator.",
|
|
162
|
+
"searchHints": [
|
|
163
|
+
"warning",
|
|
164
|
+
"DS_FIELD_WARNING_KIND",
|
|
165
|
+
"ValidationErrors",
|
|
166
|
+
"ValidationError",
|
|
167
|
+
"errors",
|
|
168
|
+
"DsFieldError",
|
|
169
|
+
"aria-invalid"
|
|
170
|
+
],
|
|
171
|
+
"surface": "typescript",
|
|
172
|
+
"detect": [
|
|
173
|
+
"warning:",
|
|
174
|
+
"'warning'",
|
|
175
|
+
"kind: 'warning'",
|
|
176
|
+
"ValidationErrors"
|
|
177
|
+
],
|
|
178
|
+
"verify": "No validator returns the key `warning` for a BLOCKING error - that kind is advisory now, so the field stays valid and a submit guard is not blocked."
|
|
179
|
+
},
|
|
180
|
+
{
|
|
181
|
+
"id": "segmented-pill-moves-to-an-inner-track",
|
|
182
|
+
"kind": "behavior",
|
|
183
|
+
"old": "ds-segmented",
|
|
184
|
+
"new": null,
|
|
185
|
+
"note": "ds-segmented now stacks a label, the pill and a message row, so the PILL moved off :host onto an inner .track. The pill's own custom properties stayed on :host and inherit down, so a token override (--ds-segmented-*) is unaffected and needs nothing. ACTION only for a ::ng-deep rule that treated the HOST as the pill — a background, a border-radius, a display:grid, a border — which now paints the whole stack instead of the control: retarget it at `ds-segmented .track`. ALSO NEW, and additive: the component provides NG_VALUE_ACCESSOR and resolves its message through resolveFieldMessage, so [(ngModel)], formControlName, signal forms, and the label / hint / error / warning / errors inputs all work as they do on the other fields. Nothing that worked before stops working.",
|
|
186
|
+
"searchHints": [
|
|
187
|
+
"ds-segmented",
|
|
188
|
+
"::ng-deep",
|
|
189
|
+
"segmented",
|
|
190
|
+
".track",
|
|
191
|
+
"--ds-segmented"
|
|
192
|
+
],
|
|
193
|
+
"surface": "style",
|
|
194
|
+
"detect": [
|
|
195
|
+
"ds-segmented",
|
|
196
|
+
"::ng-deep"
|
|
197
|
+
],
|
|
198
|
+
"verify": "Any ::ng-deep rule that painted the ds-segmented HOST as the pill - a background, a radius, a border, a display - now targets `ds-segmented .track`."
|
|
199
|
+
}
|
|
200
|
+
],
|
|
201
|
+
"informational": [
|
|
202
|
+
"ds-table's row-action kebab and column-picker trigger now read --ds-table-icon-btn-color, --ds-table-icon-btn-color-hover and --ds-table-icon-btn-focus-color, each defaulting to the value that was previously hardcoded (--icon-default, --icon-strong, --accent). Purely additive. ACTION only if you recoloured your own row trigger and are now adopting rowActions: set these three instead of repainting --icon-default globally.",
|
|
203
|
+
"ds-modal and ds-modal-card take per-side padding: --ds-modal-header-pad-top/-pad-bottom, --ds-modal-body-pad-top/-pad-bottom and --ds-modal-actions-pad-top/-pad-bottom. Each defaults to its region's existing --ds-modal-<region>-pad-y, which still works and still sets both edges, so this is purely additive and nothing moves unless you set one. ACTION only if you have been reaching past the API to pad a region asymmetrically - a rule on .modal > .header / > .body / > .actions, most likely carrying !important because the component's own padding outranks a descendant selector: that rule can now be a token on the host instead.",
|
|
204
|
+
"ds-date-picker: clearing or replacing `value` from outside now clears the picker's own typing error (typedInvalid / rangeInvalid). NO code change is required, but two workarounds can be REMOVED: (a) tearing a modal body down on `closed` just to get a fresh picker -- which never worked when the modal was reopened inside its 300ms leave animation, since the close is cancelled and `closed` never fires; (b) any manual `[error]` juggling used to mask the stale message. Blur validation is unchanged: a full-but-bad date still errors on blur.",
|
|
205
|
+
"A ds-menu inside a ds-popover now clips its rows to the panel's rounded corners, so a first or last row's fill — a hover tint, or a destructive item's red — no longer paints two square corners through the panel's rounded ones. The cause was a clip of the wrong SHAPE, not a missing one: ds-menu has overflow: hidden, but its :host-context(.popover) block flattened border-radius while leaving overflow in force. The popover now publishes --ds-menu-clip-radius (its own radius less its border) and the menu clips to that, so a brand overriding --ds-popover-radius is followed automatically. Nothing to do; --ds-menu-item-radius still defaults to 0, because the MENU owns the edge corners rather than the row.",
|
|
206
|
+
"Message inputs absorb null and undefined instead of crashing. hint, error, warning and success took a bare string and the resolver called .trim() on whatever arrived, so [error]=\"form.errors?.message\" pushed null in and threw a TypeError during render whenever the expression was empty. All four now transform at the input boundary — trimmed, with null/undefined becoming ''.",
|
|
207
|
+
"A disabled ds-icon-button variant=\"standard\" mixes its glyph toward the surface: color-mix(in srgb, <icon> 40%, var(--surface-default)), replacing the shared fixed-lightness recipe. It is the only variant with neither a fill nor a border, so the glyph carries the whole state, and the old recipe left it 1.46:1 from the enabled icon in dark (light 4.17 -> 5.19:1, dark 1.46 -> 3.58:1). Scoped to standard on purpose: filled's icon is --c-on, and white mixed into a white surface does not move. --ds-icon-button-icon-color-disabled is the same hook and still wins; only the default under it changed.",
|
|
208
|
+
"ds-field-message: the `state` input never picked an icon, though its docblock and the generated API reference both said it did (`state` \"decides colour and icon\"; `icon` \"overrides the glyph the state would pick\"). `icon` is a plain input<IconName|null>(null) with no per-state default. Behaviour is unchanged — only the documentation was wrong. If you left `icon` unset expecting a glyph from the state, pass one explicitly.",
|
|
209
|
+
"SegmentedComponent gained eight members when it joined the form systems (label, disabled, isDisabled, message, invalidResolved, fieldMessage, hintId, uid), so it is the tenth class in this release's class-surface report and the only genuinely new collision surface beyond `success`. A subclass of it declaring any of those names now fails with TS4114."
|
|
210
|
+
],
|
|
211
|
+
"deleteList": [
|
|
212
|
+
{
|
|
213
|
+
"id": "message-binding-null-guard",
|
|
214
|
+
"surface": "template",
|
|
215
|
+
"find": [
|
|
216
|
+
"?? ''",
|
|
217
|
+
"?? \"\""
|
|
218
|
+
],
|
|
219
|
+
"why": "A `?? ''` guard wrapped around a message binding - `[error]=\"form.errors?.message ?? ''\"` - added because a null pushed into `hint` / `error` / `warning` / `success` threw a TypeError during render.",
|
|
220
|
+
"replaceWith": "nothing - bind the expression directly, the inputs absorb null now"
|
|
221
|
+
}
|
|
222
|
+
]
|
|
223
|
+
}
|