@ids-group-ltd/ids-design-system 0.9.0 → 0.9.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +81 -10
- package/design-system.md +178 -7
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +36 -0
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.9.0.json +23 -2
- package/migrations/README.md +21 -12
- package/package.json +1 -1
- package/types/ids-group-ltd-ids-design-system.d.ts +21 -0
- package/migrations/unreleased/README.md +0 -134
package/migrations/0.9.0.json
CHANGED
|
@@ -126,7 +126,6 @@
|
|
|
126
126
|
"SIGNAL FORMS WORK — no adapter, no wrapper, no DS import. Put [formField] from @angular/forms/signals on any DS control and the form owns the value, validation, touched and disabled state. This was ALWAYS nearly true and nobody knew: FormValueControl requires exactly one member, a `value` model(), and every DS control already had it. Measured across all fifteen controls - thirteen bound with no library change at all. Additive, NO ACTION. WHAT CHANGED HERE, and it is why the other four rules now work too: min/max/maxLength on ds-input, ds-textarea and ds-number-stepper accept undefined on the WRITE side (the binder sends it for an unset bound; the read type is untouched); `readonly` joins ds-input, ds-textarea and ds-select as the contract spelling of the existing readOnly, because signal forms binds by NAME and a readonly() rule was reaching nothing; `minLength` and `pattern` are new native attributes on ds-input and ds-textarea; and `hidden` is declared on both control-value-accessor bases, so a hidden() rule now removes the control on all thirteen that carry one. focus() is implemented too, so focusBoundControl() - the usual way to reach the first invalid field after a failed submit - lands on the element that holds the value rather than on the host, which is a <ds-*> element and not focusable, so focus previously went nowhere. It resolves per control: the stepper's number box rather than its minus button, the tabbable radio rather than the first in the DOM, a picker's trigger rather than an input inside its closed panel. NOT implemented: dirty, pending and disabledReasons - the form still tracks them, and they are blocked on a visual decision rather than wiring. ERROR TEXT still comes from your validator: required(path.email, { message: '...' }) or a provideDsConfig field.errorMessages mapping, otherwise the field goes red with no words and only a dev warning explains why. Docs: the Practice > Signal Forms page, with a live form and the measured contract table.",
|
|
127
127
|
"ds-modal / ds-modal-card gained [dividers] (default true = today's rendering). Additive, NO ACTION - but DELETE-LIST MATERIAL if you set --ds-modal-divider: transparent. Two consumer apps did exactly that, and both were then left with header and actions padding sized to clear a rule that was no longer drawn, stacking into a 35px gap where 16px was wanted; one needed !important plus a stylelint-disable to win it back. [dividers]=\"false\" drops the rules AND the padding in one move, because those are one design decision. If you kept a deliberate --ds-modal-divider colour, nothing changes. If you set it transparent, replace it with [dividers]=\"false\" and delete whatever padding overrides you wrote afterwards - and note --ds-modal-body-pad-y now falls to 0 in that mode, so set it explicitly if you want a value in both.",
|
|
128
128
|
"ds-modal / ds-modal-card gained a [title-badge] content slot and a subtitle input, so a dialog header can carry a status chip and a second line without abandoning the component. Additive, NO ACTION - both are absent by default and the header renders exactly as before. WORTH A LOOK IF YOU HAND-ROLLED A DIALOG: a consumer audit found two screens that dropped ds-modal purely because the header could not hold `title + ds-badge` over a `carrier - type` line, and re-implemented the scrim, the body scroll lock, backdrop-click and Escape by hand - losing the focus trap, focus restore, the enter/leave animation and, in one case, the footer, which put a destructive action next to the close button. The shape matches ds-page-header: [title-badge] projects beside the title, subtitle is a plain string under it. The accessible name is still the title string - projected markup never enters aria-labelledby. Retune with --ds-modal-subtitle-text-color and --ds-modal-subtitle-font-size.",
|
|
129
|
-
"HUMAN GUIDE: migrations/unreleased/README.md walks this release in order — where to look for each change, the one call that needs judgement per table (sortMode/filterMode), and a section this project had never written before: WHAT YOU CAN NOW DELETE. Two dogfooding audits found that most consumer workarounds were written against hooks that already existed, because nothing ever told them a thing had been tokenised. Read section 3 even if the upgrade itself is clean.",
|
|
130
129
|
"NEW COMPONENT ds-field-group: several controls in one bordered box (select + input, input + button, search + date-picker). Additive, NO ACTION. If you hand-rolled a glued row by stripping borders off two controls and wrapping them, this replaces it - wrap them in <ds-field-group> and mark the stretching one with grow. Six controls can be segments: ds-input, ds-select, ds-search, ds-autocomplete, ds-date-picker, ds-button. ds-number-stepper and ds-multi-select are excluded by design. Grouped controls must not be given a label or hint - the message row would break the glued line and is suppressed.",
|
|
131
130
|
"ds-table gained [lazy] + (lazyLoad) for fetching rows as they scroll into view. Additive and opt-in, NO ACTION. If you paged a long list yourself to keep it responsive, this is the alternative: set lazy with virtualScroll and total, make data a SPARSE array total long, and write each fetched row at its ABSOLUTE index - gaps inside the window render skeleton rows. Note sortMode must not be \"client\" (it would sort only the rows that happen to have arrived); the new server default is already right.",
|
|
132
131
|
"--ds-field-height now reaches ds-autocomplete, ds-multi-select, ds-color-picker, ds-number-stepper, ds-split-button and the ds-modal confirm input. All six spelled their height as the raw --hit-* value, so the token the name advertises did nothing for them; they read the field scale now. Pixel-identical at every size EXCEPT ds-number-stepper at size=\"lg\" (its own actionable entry above). NO ACTION unless you had already worked around the gap by pinning height on one of these - that pin can go.",
|
|
@@ -152,6 +151,28 @@
|
|
|
152
151
|
"ds-table sortValue string comparison now uses sensitivity: \"base\" alongside numeric: true, so mixed-case and accented values sort together. No action; if you relied on case-sensitive ordering, pass your own sortValue returning a normalized key.",
|
|
153
152
|
"ds-date-picker keeps its trigger indicator while the panel is open (an \"open\" class alongside the focus rules). Visual only, NO ACTION. If you styled .trigger:focus-within yourself to work around the trigger going dark, you can drop it.",
|
|
154
153
|
"ds-autocomplete in single mode collapses its filter input once a value is chosen and the panel is closed, so the field reads as a picker instead of a text box. Visual only, NO ACTION. Clicking the field still opens the panel and expands the input, and typing still filters. If you set --ds-autocomplete-input-minw to work around the empty box, you can drop it.",
|
|
155
|
-
"ds-date-picker: clicking the calendar glyph no longer moves focus into the day grid. It now behaves like a click on the field - with allowInput (the default) the caret stays in the field, and a read-only field still focuses the grid. No action; ArrowDown on the field enters the grid as before. If you scripted tests that assumed a glyph click lands focus on a day button, they need updating."
|
|
154
|
+
"ds-date-picker: clicking the calendar glyph no longer moves focus into the day grid. It now behaves like a click on the field - with allowInput (the default) the caret stays in the field, and a read-only field still focuses the grid. No action; ArrowDown on the field enters the grid as before. If you scripted tests that assumed a glyph click lands focus on a day button, they need updating.",
|
|
155
|
+
"WHAT YOU CAN NOW DELETE - the half a release note usually leaves out. Two dogfooding audits (mm-ecm 2026-08-06, mm-broker 2026-08-07) read consumer stylesheets as a record of what this library made them write, and both found the same thing: most of the workarounds were written against hooks that ALREADY existed, because a release note says what broke and never says what became unnecessary. Each line below is SEARCH-FOR -> WHY IT CAN GO. None of it is required: skipping it leaves working code that is merely redundant. How to sweep for the rest: grep your styles for ::ng-deep, !important, and any selector naming a DS internal class (.button, .trigger, .option, .modal) - each hit is either an entry below or a genuine gap worth reporting.",
|
|
156
|
+
"DELETE-LIST: if you have `.button.button.button { … }` or rules against `.v-outline` / `.c-secondary` -> `ds-button` reflects `[data-variant]` and `[data-color]` on the HOST. Use `ds-button[data-variant=\"outline\"]`",
|
|
157
|
+
"DELETE-LIST: if you have `--radius-sm: 0` to square a checkbox -> `--ds-checkbox-radius`",
|
|
158
|
+
"DELETE-LIST: if you have `.title.title { font-size }` inside a modal -> `--ds-modal-title-font-size`",
|
|
159
|
+
"DELETE-LIST: if you have Pagination label type overrides -> `--ds-pagination-label-*`",
|
|
160
|
+
"DELETE-LIST: if you have `.size { display: none }` on a pager -> `[showPageSize]=\"false\"` — and it is now forwarded through `ds-table` too",
|
|
161
|
+
"DELETE-LIST: if you have `.actions:empty { display: none }` on a modal -> The library already ships it",
|
|
162
|
+
"DELETE-LIST: if you have `--ds-modal-divider: transparent`, plus whatever you rewrote the modal padding to afterwards -> `[dividers]=\"false\"` — it drops the rules *and* the padding that existed to clear them",
|
|
163
|
+
"DELETE-LIST: if you have A defensive hover rule on the selected dropdown row -> The `:not(.is-selected)` branch already handles it",
|
|
164
|
+
"DELETE-LIST: if you have `ds-menu-divider { padding: 0 }` -> `--ds-menu-divider-spacing`, which already defaults to 0",
|
|
165
|
+
"DELETE-LIST: if you have A dozen scattered `--ds-*-radius: 0` -> For a fully square brand, four lines: `--radius-sm/md/lg/xl: 0` (leave `--radius-pill`). Measured — the three ROLES alone leave options, clear buttons and dropdown panels rounded; they are the tool for squaring one family and keeping another. Worked example on the Theming page",
|
|
166
|
+
"DELETE-LIST: if you have A global rule squaring `.ds-overlay-pane` -> Radius and elevation roles now travel onto portaled panes when the host overrides them",
|
|
167
|
+
"DELETE-LIST: if you have Absolutely positioning a search glyph over an autocomplete, or hiding `.autocomplete-chevron` -> `dsAutocompletePrefix` and `[showChevron]=\"false\"`",
|
|
168
|
+
"DELETE-LIST: if you have Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it -> `clear()`",
|
|
169
|
+
"DELETE-LIST: if you have A hand-built KPI tile whose value is a badge -> `ds-stat` takes a projected `[dsStatValue]`",
|
|
170
|
+
"DELETE-LIST: if you have A pinned `--ds-search-height` (or any sibling) to get a shorter control row -> `density=\"compact\"` on the container — every field control is 32px there, measured",
|
|
171
|
+
"DELETE-LIST: if you have A hand-rolled `.scrim` + `.panel` dialog, written because the modal header could not hold a badge or a second line -> `ds-modal` projects `[title-badge]` and takes a `subtitle`. You get back the focus trap, focus restore, the scroll lock, Escape and the footer",
|
|
172
|
+
"DELETE-LIST: if you have `[value]=\"f.x().value()\" (valueChange)=\"f.x().value.set($event)\"` on every field of a signal form -> `[formField]=\"f.x\"` — the control implements the contract already",
|
|
173
|
+
"DELETE-LIST: if you have `white-space: normal` forced onto a badge in a table cell -> `--ds-badge-white-space`",
|
|
174
|
+
"DELETE-LIST: if you have `::ng-deep .card { height: 100% }` for equal-height cards -> The card's box fills a stretched host on its own",
|
|
175
|
+
"DELETE-LIST: if you have `!important` on `ds-table` cell padding under `density=\"compact\"` -> Compact no longer out-specifies the padding hooks",
|
|
176
|
+
"DELETE-LIST: if you have A wrapper around `ds-table` for sort/range announcements, keyboard column resize, or a header filter the checklist cannot express -> All three ship: the live region, the `role=\"separator\"` handle, and `dsHeaderFilter`"
|
|
156
177
|
]
|
|
157
178
|
}
|
package/migrations/README.md
CHANGED
|
@@ -27,18 +27,27 @@ at release time.
|
|
|
27
27
|
|
|
28
28
|
See `AUTHORING.md` for how to write a good entry.
|
|
29
29
|
|
|
30
|
-
**
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
the
|
|
30
|
+
**Do NOT write a prose guide per release — 0.9.0 tried it and it was retired the same day.**
|
|
31
|
+
`migrations/unreleased/README.md` restated the manifest in a form nothing reads: the auto-update
|
|
32
|
+
plugin loads `<version>.json`, and the only content the manifest did not already carry was the
|
|
33
|
+
delete-list. Worse, it went stale inside one release — three late changes never reached it — and a
|
|
34
|
+
stale duplicate misleads where no file would merely be silent. Its content now lives in the two
|
|
35
|
+
places that ARE read: the `DELETE-LIST:` entries in `<version>.json`, and a "What you can now
|
|
36
|
+
DELETE" table in that version's CHANGELOG block.
|
|
37
|
+
|
|
38
|
+
**A sibling folder `migrations/<version>/*.md` is still legal for the rare case a `note` genuinely
|
|
39
|
+
cannot hold** — a worked before/after with code on both sides, like `migrations/0.5.1/badge-statuses.md`.
|
|
40
|
+
The folder never matches the `*.json` glob, so tooling ignores it, and `tools/changelog-release.mjs`
|
|
41
|
+
promotes `migrations/unreleased/` alongside the manifest if one exists. The test before writing one:
|
|
42
|
+
**would a tool or an agent ever open it?** If the answer is "a human might", it belongs in the
|
|
43
|
+
CHANGELOG instead.
|
|
44
|
+
|
|
45
|
+
**What the manifest must carry that a release note usually omits: what the consumer can now DELETE.**
|
|
46
|
+
Two dogfooding audits (mm-ecm 08-06, mm-broker 08-07) read consumer stylesheets as a record of what
|
|
47
|
+
this library made them write, and both found the same thing — most workarounds were written against
|
|
48
|
+
hooks that ALREADY existed, because a release note says what broke and never says what became
|
|
49
|
+
unnecessary. Ship those as `DELETE-LIST: if you have <X> -> <why it can go>` entries in
|
|
50
|
+
`informational`; 0.9.0 has 21 of them and is the shape to follow.
|
|
42
51
|
|
|
43
52
|
**Authoring:** drafted at release time alongside the CHANGELOG entry (the `/changelog` workflow
|
|
44
53
|
drafts it from the release diff; the release author reviews). The prose changelog stays canonical
|
package/package.json
CHANGED
|
@@ -2713,12 +2713,21 @@ interface Cell<T> {
|
|
|
2713
2713
|
/** Internal (not public API): Hours / Minutes / AM-PM listbox columns.
|
|
2714
2714
|
* Reused by ds-time-picker's overlay and the date-picker time footer. */
|
|
2715
2715
|
declare class TimeColumnsComponent {
|
|
2716
|
+
/** Current time as `HH:mm` (24h, always — `format` changes only what is DISPLAYED). */
|
|
2716
2717
|
readonly value: _angular_core.InputSignal<string | null>;
|
|
2718
|
+
/** Display clock. `12h` adds an AM/PM column; the emitted value stays 24h either way. */
|
|
2717
2719
|
readonly format: _angular_core.InputSignal<TimeFormat>;
|
|
2720
|
+
/** Minute granularity — 15 gives four rows an hour instead of sixty. */
|
|
2718
2721
|
readonly minuteStep: _angular_core.InputSignalWithTransform<number, unknown>;
|
|
2722
|
+
/** Earliest selectable time, `HH:mm`. Earlier rows render disabled rather than being removed,
|
|
2723
|
+
* so the columns do not reflow as the bound changes. */
|
|
2719
2724
|
readonly minTime: _angular_core.InputSignal<string | null>;
|
|
2725
|
+
/** Latest selectable time, `HH:mm`. */
|
|
2720
2726
|
readonly maxTime: _angular_core.InputSignal<string | null>;
|
|
2727
|
+
/** Per-time predicate for what a range cannot express — booked slots, a lunch break.
|
|
2728
|
+
* Receives `HH:mm`; return true to disable. */
|
|
2721
2729
|
readonly disabledTime: _angular_core.InputSignal<((time: string) => boolean) | null>;
|
|
2730
|
+
/** A complete time was picked, as `HH:mm`. Not emitted while only one column has moved. */
|
|
2722
2731
|
readonly timeChange: _angular_core.OutputEmitterRef<string>;
|
|
2723
2732
|
private readonly hourButtons;
|
|
2724
2733
|
private readonly minuteButtons;
|
|
@@ -3074,6 +3083,8 @@ declare class SidenavFooterComponent {
|
|
|
3074
3083
|
readonly alertItems: _angular_core.InputSignal<readonly SidenavAlertItem[] | null>;
|
|
3075
3084
|
/** Route for the account menu's "Your profile"; empty = the item is a no-op. */
|
|
3076
3085
|
readonly profileRoute: _angular_core.InputSignal<string>;
|
|
3086
|
+
/** The collapse control was activated. The footer does not collapse itself — `ds-app-layout`
|
|
3087
|
+
* owns the rail state, so the host relays this. */
|
|
3077
3088
|
readonly collapseToggled: _angular_core.OutputEmitterRef<void>;
|
|
3078
3089
|
/** Emitted when the Alerts popover is opened, so the layout can mark-all-read. */
|
|
3079
3090
|
readonly alertsOpened: _angular_core.OutputEmitterRef<void>;
|
|
@@ -3954,7 +3965,10 @@ type DividerVariant = 'default' | 'strong' | 'vertical' | 'label';
|
|
|
3954
3965
|
type DividerSpacing = 'none' | 'sm' | 'md' | 'lg';
|
|
3955
3966
|
|
|
3956
3967
|
declare class DividerComponent {
|
|
3968
|
+
/** `default` hairline · `strong` heavier rule · `vertical` for a row · `label` to carry
|
|
3969
|
+
* projected text in the middle of the line. */
|
|
3957
3970
|
readonly variant: _angular_core.InputSignal<DividerVariant>;
|
|
3971
|
+
/** Vertical breathing room around the rule. `none` when the parent layout already owns the gap. */
|
|
3958
3972
|
readonly spacing: _angular_core.InputSignal<DividerSpacing>;
|
|
3959
3973
|
static ɵfac: _angular_core.ɵɵFactoryDeclaration<DividerComponent, never>;
|
|
3960
3974
|
static ɵcmp: _angular_core.ɵɵComponentDeclaration<DividerComponent, "ds-divider", never, { "variant": { "alias": "variant"; "required": false; "isSignal": true; }; "spacing": { "alias": "spacing"; "required": false; "isSignal": true; }; }, {}, never, ["*"], true, never>;
|
|
@@ -3987,22 +4001,29 @@ type LayoutJustify = 'start' | 'center' | 'end' | 'between';
|
|
|
3987
4001
|
type ContainerSize = DsSize | 'xl' | 'full';
|
|
3988
4002
|
|
|
3989
4003
|
declare class StackComponent {
|
|
4004
|
+
/** Space between children. `null` inherits whatever the enclosing layout set. */
|
|
3990
4005
|
readonly gap: _angular_core.InputSignal<LayoutGap | null>;
|
|
4006
|
+
/** Cross-axis alignment — horizontal, for a column. */
|
|
3991
4007
|
readonly align: _angular_core.InputSignal<LayoutAlign | null>;
|
|
3992
4008
|
static ɵfac: _angular_core.ɵɵFactoryDeclaration<StackComponent, never>;
|
|
3993
4009
|
static ɵcmp: _angular_core.ɵɵComponentDeclaration<StackComponent, "ds-stack", never, { "gap": { "alias": "gap"; "required": false; "isSignal": true; }; "align": { "alias": "align"; "required": false; "isSignal": true; }; }, {}, never, ["*"], true, never>;
|
|
3994
4010
|
}
|
|
3995
4011
|
|
|
3996
4012
|
declare class InlineComponent {
|
|
4013
|
+
/** Space between children. `null` inherits whatever the enclosing layout set. */
|
|
3997
4014
|
readonly gap: _angular_core.InputSignal<LayoutGap | null>;
|
|
4015
|
+
/** Cross-axis alignment — vertical, for a row. */
|
|
3998
4016
|
readonly align: _angular_core.InputSignal<LayoutAlign | null>;
|
|
4017
|
+
/** Main-axis distribution — horizontal, for a row. `between` pushes the ends apart. */
|
|
3999
4018
|
readonly justify: _angular_core.InputSignal<LayoutJustify | null>;
|
|
4019
|
+
/** Let the row wrap onto more lines (default). `false` keeps one line and lets it overflow. */
|
|
4000
4020
|
readonly wrap: _angular_core.InputSignalWithTransform<boolean, unknown>;
|
|
4001
4021
|
static ɵfac: _angular_core.ɵɵFactoryDeclaration<InlineComponent, never>;
|
|
4002
4022
|
static ɵcmp: _angular_core.ɵɵComponentDeclaration<InlineComponent, "ds-inline", never, { "gap": { "alias": "gap"; "required": false; "isSignal": true; }; "align": { "alias": "align"; "required": false; "isSignal": true; }; "justify": { "alias": "justify"; "required": false; "isSignal": true; }; "wrap": { "alias": "wrap"; "required": false; "isSignal": true; }; }, {}, never, ["*"], true, never>;
|
|
4003
4023
|
}
|
|
4004
4024
|
|
|
4005
4025
|
declare class ContainerComponent {
|
|
4026
|
+
/** Max content width before the container centres itself. `full` removes the cap. */
|
|
4006
4027
|
readonly size: _angular_core.InputSignal<ContainerSize>;
|
|
4007
4028
|
static ɵfac: _angular_core.ɵɵFactoryDeclaration<ContainerComponent, never>;
|
|
4008
4029
|
static ɵcmp: _angular_core.ɵɵComponentDeclaration<ContainerComponent, "ds-container", never, { "size": { "alias": "size"; "required": false; "isSignal": true; }; }, {}, never, ["*"], true, never>;
|
|
@@ -1,134 +0,0 @@
|
|
|
1
|
-
# Migrating to the next release
|
|
2
|
-
|
|
3
|
-
The manifest (`../unreleased.json`) is the terse machine mirror — what a tool applies.
|
|
4
|
-
This is the human half: **where to look, what to change, and what you can now delete.**
|
|
5
|
-
|
|
6
|
-
> **If you are on 0.7.x**, you are taking two releases at once. Read the 0.8.0 notes
|
|
7
|
-
> first; everything below is on top of them.
|
|
8
|
-
|
|
9
|
-
---
|
|
10
|
-
|
|
11
|
-
## 1. What breaks — eight things, by where you will find them
|
|
12
|
-
|
|
13
|
-
Work through them in this order. The first three are one rename and are best done together.
|
|
14
|
-
|
|
15
|
-
### In your templates
|
|
16
|
-
|
|
17
|
-
| Look for | Change to | Notes |
|
|
18
|
-
| --- | --- | --- |
|
|
19
|
-
| `<ds-auth-shell>` | `<ds-auth-layout>` | Inputs, outputs and slots all keep their names |
|
|
20
|
-
| `sortMode` / `filterMode` **absent** on a `ds-table` | Add `sortMode="client"` (and `filterMode="client"`) **if the table holds every row** | The default flipped to `"server"`. See §2 |
|
|
21
|
-
|
|
22
|
-
### In your TypeScript
|
|
23
|
-
|
|
24
|
-
| Look for | Change to |
|
|
25
|
-
| --- | --- |
|
|
26
|
-
| `AuthShellComponent` | `AuthLayoutComponent` |
|
|
27
|
-
|
|
28
|
-
### In your stylesheets
|
|
29
|
-
|
|
30
|
-
| Look for | Change to | Notes |
|
|
31
|
-
| --- | --- | --- |
|
|
32
|
-
| `--ds-auth-shell-*` | `--ds-auth-layout-*` | Six tokens. **Do not** rename `--auth-card-w` — it carries no such prefix |
|
|
33
|
-
| `--search-h` | `--ds-search-height`, or `--ds-field-height` for the whole family | The global token is gone; a declaration of it is now inert |
|
|
34
|
-
|
|
35
|
-
### Visual changes to eyeball
|
|
36
|
-
|
|
37
|
-
- **`ds-search` is 40px tall, was 36px.** It was the only control in the library on that
|
|
38
|
-
height. Restore with `ds-search { --ds-search-height: 36px; }` if your toolbar depends
|
|
39
|
-
on it — but see §3 first, because a pin may not be what you want.
|
|
40
|
-
- **`ds-number-stepper` at `size="lg"` is 48px, was 44px.** Other sizes unchanged.
|
|
41
|
-
|
|
42
|
-
### Worth a deliberate pass, not a find/replace
|
|
43
|
-
|
|
44
|
-
- **Signal Forms bind to DS controls.** `<ds-input [formField]="f.email" />` — that is the whole
|
|
45
|
-
integration; `[formField]` comes from `@angular/forms/signals`, not from this library. Thirteen
|
|
46
|
-
of fifteen controls already bound before this release; the other two, and the `readonly()`,
|
|
47
|
-
`pattern()`, `minLength()` and `hidden()` rules, work now. If you hand-bound
|
|
48
|
-
`[value]="f.x().value()" (valueChange)="f.x().value.set($event)"` per field, **all of that can
|
|
49
|
-
go.** Give each validator a `message`, or map the kinds once in `provideDsConfig`, or the field
|
|
50
|
-
turns red with no words. See the Practice → Signal Forms page.
|
|
51
|
-
|
|
52
|
-
- **`ds-tabs` can now own the URL.** Set `urlParam="tab"` and the active tab survives F5,
|
|
53
|
-
a shared link and the Back button. Per strip: give each `ds-tab` a `value` (the URL is
|
|
54
|
-
written from it, so without one your links carry the visible label and break when it is
|
|
55
|
-
reworded), use **one parameter name per strip** (two strips sharing a name erase each
|
|
56
|
-
other — there is a dev warning), and delete any hand-rolled `queryParamMap` + `navigate()`
|
|
57
|
-
wiring, which would otherwise fight it.
|
|
58
|
-
|
|
59
|
-
---
|
|
60
|
-
|
|
61
|
-
## 2. The one that needs judgement per table
|
|
62
|
-
|
|
63
|
-
`sortMode` and `filterMode` default to `'server'` now, where they used to default to
|
|
64
|
-
`'client'`.
|
|
65
|
-
|
|
66
|
-
**Why it changed:** server-paged is the normal case, and there the old default was
|
|
67
|
-
actively wrong — the table sorted the page in hand, so rows looked sorted and were not.
|
|
68
|
-
|
|
69
|
-
**How to decide, per table:**
|
|
70
|
-
|
|
71
|
-
- **Binds `total`?** It is server-paged. The new default is what you wanted; do nothing.
|
|
72
|
-
- **Does not bind `total`?** It almost certainly holds every row. Add `sortMode="client"`,
|
|
73
|
-
and `filterMode="client"` if any column has `filter: 'set'` — otherwise the headers stay
|
|
74
|
-
clickable and do nothing.
|
|
75
|
-
|
|
76
|
-
**How to find them all:** run the app in dev and read the console. A reversed dev warning
|
|
77
|
-
now fires on exactly the case that needs your attention (no `total`, sortable or filterable
|
|
78
|
-
columns, no declared mode) and names each table.
|
|
79
|
-
|
|
80
|
-
---
|
|
81
|
-
|
|
82
|
-
## 3. What you can now DELETE — the half a migration guide usually leaves out
|
|
83
|
-
|
|
84
|
-
Two dogfooding audits (mm-ecm 2026-08-06, mm-broker 2026-08-07) read consumer stylesheets
|
|
85
|
-
as a record of what this library made them write. Both found the same thing: **most of the
|
|
86
|
-
workarounds were written against hooks that already existed** — the consumer had no signal
|
|
87
|
-
that anything had been tokenised since. That is a failure of these notes, not of the
|
|
88
|
-
consumer, so here is the list.
|
|
89
|
-
|
|
90
|
-
Search your styles for these; if you find them, they can go.
|
|
91
|
-
|
|
92
|
-
| If you have | Delete it, because |
|
|
93
|
-
| --- | --- |
|
|
94
|
-
| `.button.button.button { … }` or rules against `.v-outline` / `.c-secondary` | `ds-button` reflects `[data-variant]` and `[data-color]` on the HOST. Use `ds-button[data-variant="outline"]` |
|
|
95
|
-
| `--radius-sm: 0` to square a checkbox | `--ds-checkbox-radius` |
|
|
96
|
-
| `.title.title { font-size }` inside a modal | `--ds-modal-title-font-size` |
|
|
97
|
-
| Pagination label type overrides | `--ds-pagination-label-*` |
|
|
98
|
-
| `.size { display: none }` on a pager | `[showPageSize]="false"` — and it is now forwarded through `ds-table` too |
|
|
99
|
-
| `.actions:empty { display: none }` on a modal | The library already ships it |
|
|
100
|
-
| `--ds-modal-divider: transparent`, plus whatever you rewrote the modal padding to afterwards | `[dividers]="false"` — it drops the rules *and* the padding that existed to clear them |
|
|
101
|
-
| A defensive hover rule on the selected dropdown row | The `:not(.is-selected)` branch already handles it |
|
|
102
|
-
| `ds-menu-divider { padding: 0 }` | `--ds-menu-divider-spacing`, which already defaults to 0 |
|
|
103
|
-
| A dozen scattered `--ds-*-radius: 0` | For a fully square brand, four lines: `--radius-sm/md/lg/xl: 0` (leave `--radius-pill`). Measured — the three ROLES alone leave options, clear buttons and dropdown panels rounded; they are the tool for squaring one family and keeping another. Worked example on the Theming page |
|
|
104
|
-
| A global rule squaring `.ds-overlay-pane` | Radius and elevation roles now travel onto portaled panes when the host overrides them |
|
|
105
|
-
| Absolutely positioning a search glyph over an autocomplete, or hiding `.autocomplete-chevron` | `dsAutocompletePrefix` and `[showChevron]="false"` |
|
|
106
|
-
| Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it | `clear()` |
|
|
107
|
-
| A hand-built KPI tile whose value is a badge | `ds-stat` takes a projected `[dsStatValue]` |
|
|
108
|
-
| A pinned `--ds-search-height` (or any sibling) to get a shorter control row | `density="compact"` on the container — every field control is 32px there, measured |
|
|
109
|
-
| A hand-rolled `.scrim` + `.panel` dialog, written because the modal header could not hold a badge or a second line | `ds-modal` projects `[title-badge]` and takes a `subtitle`. You get back the focus trap, focus restore, the scroll lock, Escape and the footer |
|
|
110
|
-
| `[value]="f.x().value()" (valueChange)="f.x().value.set($event)"` on every field of a signal form | `[formField]="f.x"` — the control implements the contract already |
|
|
111
|
-
| `white-space: normal` forced onto a badge in a table cell | `--ds-badge-white-space` |
|
|
112
|
-
| `::ng-deep .card { height: 100% }` for equal-height cards | The card's box fills a stretched host on its own |
|
|
113
|
-
| `!important` on `ds-table` cell padding under `density="compact"` | Compact no longer out-specifies the padding hooks |
|
|
114
|
-
| A wrapper around `ds-table` for sort/range announcements, keyboard column resize, or a header filter the checklist cannot express | All three ship: the live region, the `role="separator"` handle, and `dsHeaderFilter` |
|
|
115
|
-
|
|
116
|
-
**How to check you got them all:** grep your styles for `::ng-deep`, `!important` and any
|
|
117
|
-
selector naming a DS internal class (`.button`, `.trigger`, `.option`, `.modal`). Each hit
|
|
118
|
-
is either a genuine gap worth reporting or an entry in the table above.
|
|
119
|
-
|
|
120
|
-
---
|
|
121
|
-
|
|
122
|
-
## 4. After you bump
|
|
123
|
-
|
|
124
|
-
- **Run the app in dev with the console open.** The library warns about the combinations it
|
|
125
|
-
cannot fix for you: undeclared sort/filter mode, duplicate `urlParam`, lazy without
|
|
126
|
-
`virtualScroll`, an unknown icon name, a projected stat value with an orphaned `unit`.
|
|
127
|
-
Every warning names the component and what to do.
|
|
128
|
-
- **Check a toolbar and a form row side by side.** The field-height contract moved
|
|
129
|
-
`ds-search`, so anything you had lined up by hand is worth a second look. If you pin
|
|
130
|
-
heights per component, consider `[data-density]` instead — it retunes the whole family at
|
|
131
|
-
once and survives the next change of this kind.
|
|
132
|
-
- **Tell us what you had to hand-roll.** The delete list in §3 exists because two consumers
|
|
133
|
-
wrote forty lines of workarounds against hooks that were already there. If you are
|
|
134
|
-
reaching into a DS internal, that is a gap worth filing.
|