@ids-group-ltd/ids-design-system 0.14.7 → 0.15.0
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 +735 -230
- package/components.md +64 -25
- package/docs/agent/INDEX.md +3 -1
- package/docs/agent/charts/ds-bar-chart.md +7 -4
- package/docs/agent/charts/ds-chart.md +1 -1
- package/docs/agent/charts/ds-column-chart.md +1 -1
- package/docs/agent/charts/ds-funnel-chart.md +1 -1
- package/docs/agent/charts/ds-pie-chart.md +1 -1
- package/docs/agent/charts/ds-waterfall-chart.md +2 -2
- package/docs/agent/feedback/ds-loading-overlay.md +2 -0
- package/docs/agent/feedback/ds-skeleton.md +1 -1
- package/docs/agent/forms/ds-button.md +2 -2
- package/docs/agent/forms/ds-date-picker.md +1 -0
- package/docs/agent/foundations/global-helper-classes.md +3 -3
- package/docs/agent/overlays/ds-bottom-sheet.md +1 -1
- package/docs/agent/overlays/ds-definition-term.md +10 -0
- package/docs/agent/overlays/ds-drawer.md +1 -1
- package/docs/agent/overlays/ds-info-hint.md +10 -0
- package/docs/agent/overlays/ds-menu.md +1 -1
- package/docs/agent/overlays/ds-modal-card.md +1 -1
- package/docs/agent/overlays/ds-modal.md +19 -1
- package/docs/agent/overlays/ds-tooltip-panel.md +1 -1
- package/docs/agent/overlays/ds-tooltip.md +3 -3
- package/docs/agent/tables/ds-table.md +3 -2
- package/eslint/deprecated-api.json +889 -0
- package/eslint/index.mjs +394 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs +6 -12
- package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs +19 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar-group.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs +169 -37
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-bottom-sheet.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-bottom-sheet.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-button-group.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-button-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-calendar-day.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-calendar-day.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-card.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-card.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-data-table.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-data-table.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs +195 -27
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart.mjs +23 -20
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs +9 -9
- package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs +107 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-divider.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-divider.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs +5 -15
- package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-field-message.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-field-message.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs +11 -8
- package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-heatmap-chart.mjs +4 -3
- package/fesm2022/ids-group-ltd-ids-design-system-components-heatmap-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs +44 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-layout.mjs +6 -6
- package/fesm2022/ids-group-ltd-ids-design-system-components-layout.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs +10 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-loading-overlay.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-loading-overlay.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs +136 -29
- package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +21 -26
- package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs +19 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-page-footer.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-page-footer.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-page-header.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-page-header.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-password-rules.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-password-rules.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-pie-chart.mjs +8 -6
- package/fesm2022/ids-group-ltd-ids-design-system-components-pie-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-scatter-chart.mjs +19 -5
- package/fesm2022/ids-group-ltd-ids-design-system-components-scatter-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs +21 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs +6 -6
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-sparkline.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-sparkline.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-spinner.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-spinner.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-status-dot.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-status-dot.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +223 -8
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs +410 -145
- package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-topbar.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-topbar.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-waterfall-chart.mjs +14 -11
- package/fesm2022/ids-group-ltd-ids-design-system-components-waterfall-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs +86 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs +18 -81
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-overlay.mjs +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-overlay.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +2 -0
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.10.0.json +79 -21
- package/migrations/0.10.1.json +38 -21
- package/migrations/0.10.2.json +44 -7
- package/migrations/0.10.3.json +7 -5
- package/migrations/0.11.0.json +10 -7
- package/migrations/0.11.1.json +25 -14
- package/migrations/0.11.2.json +3 -3
- package/migrations/0.11.3.json +9 -6
- package/migrations/0.11.4.json +13 -12
- package/migrations/0.12.1.json +41 -14
- package/migrations/0.12.2.json +7 -6
- package/migrations/0.12.3.json +3 -3
- package/migrations/0.13.0.json +11 -11
- package/migrations/0.13.1.json +60 -8
- package/migrations/0.13.2.json +98 -44
- package/migrations/0.13.3.json +46 -16
- package/migrations/0.13.4.json +23 -22
- package/migrations/0.14.0.json +5 -5
- package/migrations/0.14.1.json +5 -5
- package/migrations/0.14.2.json +1 -1
- package/migrations/0.14.4.json +6 -5
- package/migrations/0.14.5.json +13 -7
- package/migrations/0.14.6.json +2 -2
- package/migrations/0.14.8.json +56 -0
- package/migrations/0.15.0.json +999 -0
- package/migrations/0.2.0.json +2 -2
- package/migrations/0.3.0.json +43 -6
- package/migrations/0.4.0.json +95 -13
- package/migrations/0.5.0.json +116 -10
- package/migrations/0.5.1.json +97 -11
- package/migrations/0.6.0.json +30 -1
- package/migrations/0.6.1.json +22 -1
- package/migrations/0.6.2.json +8 -4
- package/migrations/0.6.3.json +17 -5
- package/migrations/0.7.0.json +58 -9
- package/migrations/0.7.1.json +62 -8
- package/migrations/0.8.0.json +60 -12
- package/migrations/0.9.0.json +68 -25
- package/migrations/0.9.1.json +1 -1
- package/migrations/README.md +57 -3
- package/package.json +19 -1
- package/schematics/check-overrides/index.cjs +4 -11
- package/schematics/check-overrides/scan.cjs +12 -1
- package/schematics/check-overrides/surface.json +51 -10
- package/schematics/ng-add/index.cjs +7 -1
- package/stylelint/deprecated-tokens.json +2697 -0
- package/stylelint/index.mjs +94 -0
- package/stylelint/since-version.mjs +26 -0
- package/styles/_chart-motion.scss +3 -9
- package/styles/_chip-row.scss +5 -2
- package/styles/_clear-button.scss +2 -0
- package/styles/_component-base.scss +56 -0
- package/styles/_dismiss-button.scss +16 -0
- package/styles/_dropdown-overlay.scss +19 -0
- package/styles/_focus.scss +4 -1
- package/styles/_overlay-motion.scss +4 -6
- package/styles/_pinned.scss +43 -0
- package/styles/_skeleton-shimmer.scss +2 -8
- package/styles/_table-controls.scss +4 -0
- package/styles/_target.scss +40 -0
- package/styles/_text-clip.scss +23 -4
- package/styles/_tokens.scss +0 -1
- package/styles/_typography.scss +2 -0
- package/styles/_visually-hidden.scss +2 -0
- package/styles/ds.scss +0 -1
- package/themes/README.md +7 -7
- package/types/ids-group-ltd-ids-design-system-components-autocomplete.d.ts +4 -1
- package/types/ids-group-ltd-ids-design-system-components-bar-chart.d.ts +74 -4
- package/types/ids-group-ltd-ids-design-system-components-button.d.ts +2 -2
- package/types/ids-group-ltd-ids-design-system-components-chart-tooltip.d.ts +40 -4
- package/types/ids-group-ltd-ids-design-system-components-chart.d.ts +8 -3
- package/types/ids-group-ltd-ids-design-system-components-column-chart.d.ts +4 -3
- package/types/ids-group-ltd-ids-design-system-components-definition-term.d.ts +22 -0
- package/types/ids-group-ltd-ids-design-system-components-drawer.d.ts +0 -1
- package/types/ids-group-ltd-ids-design-system-components-funnel-chart.d.ts +7 -3
- package/types/ids-group-ltd-ids-design-system-components-heatmap-chart.d.ts +1 -0
- package/types/ids-group-ltd-ids-design-system-components-info-hint.d.ts +14 -0
- package/types/ids-group-ltd-ids-design-system-components-line-chart.d.ts +5 -0
- package/types/ids-group-ltd-ids-design-system-components-menu.d.ts +8 -3
- package/types/ids-group-ltd-ids-design-system-components-modal.d.ts +0 -2
- package/types/ids-group-ltd-ids-design-system-components-multi-select.d.ts +4 -1
- package/types/ids-group-ltd-ids-design-system-components-pie-chart.d.ts +5 -3
- package/types/ids-group-ltd-ids-design-system-components-scatter-chart.d.ts +13 -3
- package/types/ids-group-ltd-ids-design-system-components-select.d.ts +4 -1
- package/types/ids-group-ltd-ids-design-system-components-table.d.ts +30 -3
- package/types/ids-group-ltd-ids-design-system-components-tooltip.d.ts +48 -17
- package/types/ids-group-ltd-ids-design-system-components-waterfall-chart.d.ts +6 -2
- package/types/ids-group-ltd-ids-design-system-components.d.ts +26 -2
- package/types/ids-group-ltd-ids-design-system-core.d.ts +7 -11
- package/types/ids-group-ltd-ids-design-system.d.ts +3 -1
package/migrations/0.8.0.json
CHANGED
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
"old": "ds-table[clientSort]",
|
|
8
8
|
"new": "sortMode",
|
|
9
9
|
"action": "`[clientSort]=\"true\"` and a bare `clientSort` become `sortMode=\"client\"`; `[clientSort]=\"false\"` or `[clientSort]=\"expr\"` becomes `[sortMode]=\"expr ? 'client' : 'server'\"`. A table that had NO clientSort binding and reorders in its own `(sortChange)` handler must declare `sortMode=\"server\"`. A table that renders a sortable column but sorts nowhere declares `sortMode=\"none\"`, which drops the button, the caret and `aria-sort` instead of leaving a dead control. TypeScript callers can type the value with `import type { TableSortMode }`.",
|
|
10
|
-
"pitfall": "The last case is the one that is not a find/replace, because the DEFAULT CHANGED: unset resolves to `client` at this version. A server-paged table that only emitted `sortChange` will now ALSO sort its own rows — and client sorting reorders the current page only, so the rows look sorted and are not. Dev builds warn
|
|
10
|
+
"pitfall": "The last case is the one that is not a find/replace, because the DEFAULT CHANGED: unset resolves to `client` at this version. A server-paged table that only emitted `sortChange` will now ALSO sort its own rows — and client sorting reorders the current page only, so the rows look sorted and are not. Dev builds warn when `total` is set, a column is sortable and `sortMode` is unset, but a production build says nothing.",
|
|
11
11
|
"note": "The boolean could not express \"nothing sorts\", so a column marked `sortable: true` on a table with no sorting drew a header that looked live, showed a caret on hover and did nothing.",
|
|
12
12
|
"searchHints": [
|
|
13
13
|
"clientSort",
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
"ds-table"
|
|
20
20
|
],
|
|
21
21
|
"surface": "template",
|
|
22
|
-
"verify": "No `clientSort` is left anywhere. Every server-paged `<ds-table>` - one that binds `total` and reorders in its own (sortChange) - declares sortMode=\"server\" EXPLICITLY: at this version an unset sortMode resolves to \"client\", so leaving it off makes the table re-sort the page it is showing and the rows look sorted while the server order is unchanged. A table holding all its rows declares sortMode=\"client\" or leaves it unset; a table that sorts nothing declares sortMode=\"none\". Dev builds warn on total
|
|
22
|
+
"verify": "No `clientSort` is left anywhere. Every server-paged `<ds-table>` - one that binds `total` and reorders in its own (sortChange) - declares sortMode=\"server\" EXPLICITLY: at this version an unset sortMode resolves to \"client\", so leaving it off makes the table re-sort the page it is showing and the rows look sorted while the server order is unchanged. A table holding all its rows declares sortMode=\"client\" or leaves it unset; a table that sorts nothing declares sortMode=\"none\". Dev builds warn on total with sortMode unset, never on an explicit sortMode=\"client\".",
|
|
23
23
|
"restore": "sortMode=\"server\" on a table that should only emit (sortChange) and sort nothing itself"
|
|
24
24
|
},
|
|
25
25
|
{
|
|
@@ -30,7 +30,7 @@
|
|
|
30
30
|
"action": "Build after upgrading — the compiler enumerates every collision. Per member: rename your own, or add `override` where the base semantics genuinely match. A subclass that overrode `messageState` should move its logic to an `error` or `warning` binding on the element instead, since the message is resolved centrally now.",
|
|
31
31
|
"appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users of the `<ds-…>` elements need nothing.",
|
|
32
32
|
"pitfall": "A PRIVATE member collides too — TS2415 — and `TableComponent.saveLayout()` is the likeliest to collide, because a table wrapper commonly declares the same name. Two more shapes hide here: this release REMOVES members as well as adding them (the fourteen fields dropped protected `messageState`, DatePicker also `messageText`, and Checkbox, Switch and Radio dropped protected `devMode`), so an `override` can start naming nothing; and `close()` gained an optional `cause`, which an override declared as `close()` still satisfies — only a subclass that re-declares the parameter list differently breaks.",
|
|
33
|
-
"note": "Additions: the fourteen field classes gained the `error`, `warning`, `errors` and `touched` inputs
|
|
33
|
+
"note": "Additions: the fourteen field classes gained the `error`, `warning`, `errors` and `touched` inputs, protected `message`, `invalidResolved` and private `fieldMessage`; InputComponent also `ariaDescribedBy` and protected `describedBy`; DatePickerComponent private `localError`, `dateInvalid`; both CVA bases protected `touchedSelf`; AppLayoutComponent `railOverlay`, `railId` and the `restoreScroll` / `restoreScrollTimeout` inputs; TableComponent lost `clientSort` and gained `sortModeResolved`, `sortableCol()`, `exporting`, `runExport()`, `virtualizing`, `virtualRowHeight`, `virtualWindow`, `windowData`, `isStriped()`, the `sortMode`, `persistLayout`, `storageKey`, `exportButton`, `exportFilename`, `exportFetcher`, `virtualScroll`, `virtualRowSize` inputs and private `saveLayout()`, `restoreLayout()`, `layoutKey()`, `layoutRestored`, `scrollTop`, `viewportHeight`; ButtonComponent `ariaControls`; IconButtonComponent `ariaExpanded`, `ariaControls`; LayoutScrollService `scroller`, `scrollTo()`, `configureRestore()`, `consumePendingOffset()`, `contentReady()` and fifteen private restore members, dropping private `scrollContainer`. Every field class also lost `messageState`; `CheckboxComponent`, `RadioComponent` and `SwitchComponent` lost `devMode`, and `DatePickerComponent` lost `messageText`. `LayoutScrollService` gained 20 in all.",
|
|
34
34
|
"searchHints": [
|
|
35
35
|
"extends InputComponent",
|
|
36
36
|
"extends SelectComponent",
|
|
@@ -53,7 +53,42 @@
|
|
|
53
53
|
"extends InputComponent",
|
|
54
54
|
"extends TableComponent",
|
|
55
55
|
"extends ",
|
|
56
|
-
"saveLayout"
|
|
56
|
+
"saveLayout",
|
|
57
|
+
"InputComponent",
|
|
58
|
+
"extends AppLayoutComponent",
|
|
59
|
+
"AppLayoutComponent",
|
|
60
|
+
"extends AutocompleteComponent",
|
|
61
|
+
"AutocompleteComponent",
|
|
62
|
+
"extends ButtonComponent",
|
|
63
|
+
"ButtonComponent",
|
|
64
|
+
"extends CheckboxComponent",
|
|
65
|
+
"CheckboxComponent",
|
|
66
|
+
"extends ColorPickerComponent",
|
|
67
|
+
"ColorPickerComponent",
|
|
68
|
+
"extends DatePickerComponent",
|
|
69
|
+
"DatePickerComponent",
|
|
70
|
+
"extends IconButtonComponent",
|
|
71
|
+
"IconButtonComponent",
|
|
72
|
+
"extends LayoutScrollService",
|
|
73
|
+
"LayoutScrollService",
|
|
74
|
+
"extends MultiSelectComponent",
|
|
75
|
+
"MultiSelectComponent",
|
|
76
|
+
"extends OtpInputComponent",
|
|
77
|
+
"OtpInputComponent",
|
|
78
|
+
"extends RadioComponent",
|
|
79
|
+
"RadioComponent",
|
|
80
|
+
"extends RadioGroupComponent",
|
|
81
|
+
"RadioGroupComponent",
|
|
82
|
+
"extends SelectComponent",
|
|
83
|
+
"SelectComponent",
|
|
84
|
+
"extends SliderComponent",
|
|
85
|
+
"SliderComponent",
|
|
86
|
+
"extends SwitchComponent",
|
|
87
|
+
"SwitchComponent",
|
|
88
|
+
"extends TextareaComponent",
|
|
89
|
+
"TextareaComponent",
|
|
90
|
+
"extends TimePickerComponent",
|
|
91
|
+
"TimePickerComponent"
|
|
57
92
|
],
|
|
58
93
|
"verify": "A typecheck reports no TS4114 / TS2415 / TS2416 on any class extending a DS component - including a PRIVATE collision (saveLayout / restoreLayout on the table) and a subclass that overrode the removed protected `messageState`."
|
|
59
94
|
},
|
|
@@ -80,10 +115,9 @@
|
|
|
80
115
|
"kind": "class-rename",
|
|
81
116
|
"old": "ds-radio-group .group-label",
|
|
82
117
|
"new": ".label",
|
|
83
|
-
"action": "Retarget `.group-label` to `.label` under ds-radio-group
|
|
84
|
-
"appliesWhen": "
|
|
118
|
+
"action": "Retarget `.group-label` to `.label` under ds-radio-group.",
|
|
119
|
+
"appliesWhen": "Only a rule of yours scoped under ds-radio-group that names `.group-label`. The label's new type is `radio-group-label-type-joins-field-labels`.",
|
|
85
120
|
"pitfall": "`.group-label` is ALSO the class `ds-sidenav-group` uses for its heading, and that one is unchanged. A repo-wide rename takes the sidenav heading with it. Only rules scoped under ds-radio-group are affected.",
|
|
86
|
-
"note": "Two changes to one element: the class, and the type — the label draws `--font-weight-bold` at `--font-size-xs` now instead of its own medium weight at `--font-size-s`. It was the only field label drawing its own, and beside an input it read as a different kind of element.",
|
|
87
121
|
"searchHints": [
|
|
88
122
|
"group-label",
|
|
89
123
|
".group-label",
|
|
@@ -91,8 +125,22 @@
|
|
|
91
125
|
"radio-group",
|
|
92
126
|
"label"
|
|
93
127
|
],
|
|
128
|
+
"surface": "style"
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"id": "radio-group-label-type-joins-field-labels",
|
|
132
|
+
"kind": "behavior",
|
|
133
|
+
"old": "ds-radio-group",
|
|
134
|
+
"new": null,
|
|
135
|
+
"action": "None, unless a screen needs the old look: scope the family tokens and set the line height, which has no hook, as in `restore`.",
|
|
136
|
+
"appliesWhen": "Every ds-radio-group label. None of this is needed for most screens — matching the family is the point of the change.",
|
|
137
|
+
"note": "The label draws `--font-weight-bold` at `--font-size-xs` on `--line-height-base` now instead of its own medium weight at `--font-size-s` on `--line-height-flat`. It was the only field label drawing its own, and beside an input it read as a different kind of element.",
|
|
138
|
+
"searchHints": [
|
|
139
|
+
"ds-radio-group"
|
|
140
|
+
],
|
|
94
141
|
"surface": "style",
|
|
95
|
-
"
|
|
142
|
+
"verify": "A ds-radio-group label renders at the weight, size and line height of a ds-input label beside it, or at the old medium weight and size where the restore snippet is in place.",
|
|
143
|
+
"restore": "ds-radio-group { --ds-field-label-weight: var(--font-weight-medium); --ds-field-label-font-size: var(--font-size-s); } ds-radio-group > .label[class] { line-height: var(--line-height-flat); }"
|
|
96
144
|
},
|
|
97
145
|
{
|
|
98
146
|
"id": "ng-add-schematic-now-loads",
|
|
@@ -216,15 +264,15 @@
|
|
|
216
264
|
],
|
|
217
265
|
"informational": [
|
|
218
266
|
"Every field gained `error` and `warning` beside `hint`, resolved on a fixed ladder: `error` (an explicit string, shown at once) → validation errors → `warning` → `hint`. Only ONE line renders, so a field's height does not depend on how many sources are populated. Purely additive: a field that binds only `hint` behaves exactly as before, and when something is invalid but no source produced text the `hint` still renders in the error state — so the pre-existing `[invalid]` + `[hint]=\"errorText\"` idiom keeps working untouched.",
|
|
219
|
-
"Fields now read validation state from the bound form control, so `error` is optional. Signal forms binds `errors` and `touched` automatically (those input names are Angular 21's `FormUiControl` contract) and already drove the value through the `ControlValueAccessor` DS fields have always implemented. Reactive and template-driven forms need NO new binding: the field resolves `NgControl` after first render and subscribes to `control.events`. Errors wait for the first blur, or for the parent form to be submitted, so a `required` error never greets an untouched form. `invalid` is now OR-ed with what the control reports
|
|
220
|
-
"`DS_CONFIG` gained `field.errorMessages` — one shared map from validation-error kind to text, for errors whose validator carried no message (Angular's built-ins never do). A message on the error itself always wins, so `required(path, { message })` in signal forms or `{ myError: 'text' }` from a plain validator overrides the map per case. An error that resolves to no text anywhere warns in dev
|
|
267
|
+
"Fields now read validation state from the bound form control, so `error` is optional. Signal forms binds `errors` and `touched` automatically (those input names are Angular 21's `FormUiControl` contract) and already drove the value through the `ControlValueAccessor` DS fields have always implemented. Reactive and template-driven forms need NO new binding: the field resolves `NgControl` after first render and subscribes to `control.events`. Errors wait for the first blur, or for the parent form to be submitted, so a `required` error never greets an untouched form. `invalid` is now OR-ed with what the control reports: `[invalid]=\"true\"` forces the error state, `false` cannot clear one the control reports.",
|
|
268
|
+
"`DS_CONFIG` gained `field.errorMessages` — one shared map from validation-error kind to text, for errors whose validator carried no message (Angular's built-ins never do). A message on the error itself always wins, so `required(path, { message })` in signal forms or `{ myError: 'text' }` from a plain validator overrides the map per case. An error that resolves to no text anywhere warns in dev; the field still turns invalid (error styling, aria-invalid) and shows its warning or hint instead, or with neither no message at all.",
|
|
221
269
|
"`dsRailTrigger` is a new directive: put it on your own burger anywhere inside `ds-app-layout` and it toggles `[(railOpen)]` and keeps `aria-expanded` / `aria-controls` pointing at the rail panel, so the trigger and the panel are related for a screen reader. Both attributes are dropped while the rail is not an overlay, where `aria-expanded=\"false\"` would contradict what the user sees. `ds-app-layout` also exposes `railId` and the read-only `railOverlay` signal for a consumer that builds its own trigger.",
|
|
222
270
|
"`ds-table` `sortMode=\"none\"` is the way to render a column that is sortable in principle but not on this screen: the header renders as plain text, with no button, caret or `aria-sort`, instead of a control that does nothing.",
|
|
223
271
|
"Bugfix, no action: a CLOSED compact `ds-app-layout` rail is now `inert`, and closing it (Escape, scrim click, navigation) returns focus to the control that claims the rail via `aria-controls`. Before, the off-canvas panel kept `role=\"dialog\"`/`aria-modal=\"true\"`, left every nav link tabbable and stranded the caret inside the hidden panel, because cdkTrapFocusAutoCapture restores focus only on directive destroy. A consumer whose custom burger sets neither `dsRailTrigger` nor `aria-controls` gets the inert fix but no focus return - add `aria-controls` pointing at `ds-app-layout`'s `railId` to get it.",
|
|
224
272
|
"Bugfix, no action: NESTING one `ds-app-layout` inside another now works. Three separate faults are fixed. (1) The rail's open state was written as `:host(.rail-open) &`, which Angular's emulated encapsulation compiles to a DESCENDANT selector, and every instance of a component shares one encapsulation attribute — so an inner layout's rail opened whenever an outer one was open, and the inner scrim swallowed clicks meant for the outer. The state now lives on the elements it styles (`.rail.open` / `.scrim.open`). (2) Below `lg` the rail was `position: fixed`, resolving against the viewport, so an embedded layout threw its rail over the top-left of the WINDOW; rail and scrim are now `absolute` against a `position: relative` host. (3) The host now also sets `isolation: isolate`, so each layout z-indexes its rail (`--layer-drawer`) and scrim in its own stacking context instead of the one root context, where an inner layout's rail could paint over an outer layout's open rail. All three are identical to the old behaviour for a single full-viewport shell, which is the normal case.",
|
|
225
273
|
"Bugfix, no action: `--ds-overlay-enter-scale` is now forwarded onto the portaled overlay pane, so scoping it per instance (`ds-select { --ds-overlay-enter-scale: 0.9; }`) finally reaches select / multi-select / autocomplete / date / time / colour picker / popover / tooltip / menu-submenu panels. 0.7.1 shipped it as a known gap — the token was resolved on the pane but absent from the forwarded set, while the other four enter tokens did forward. A GLOBAL override worked before and is unaffected.",
|
|
226
|
-
"The field family gained one label contract: --ds-field-label-font-size / -weight / -color / -transform / -tracking, resolved by ds-input, ds-textarea, ds-select, ds-date-picker, ds-time-picker and ds-radio-group through a shared mixin. Defaults equal the values
|
|
227
|
-
"`--ds-field-height` is new, and the --field-h-sm/-md/-lg scale is now actually read by ds-input, ds-select, ds-date-picker and ds-time-picker - previously only -lg was, the other two sizes reaching past the scale to the raw --hit-min/--hit-cozy. Values are identical, so no height moves on upgrade. NO ACTION, but two things become possible that silently did nothing before: retuning --field-h-md (or -sm) now moves every field, and --ds-field-height pins one height regardless of the size class, scopable per component. NOT a fix for unequal picker heights - those were already equal as of 0.7.1's aligned trigger geometry.",
|
|
274
|
+
"The field family gained one label contract: --ds-field-label-font-size / -weight / -color / -transform / -tracking, resolved by ds-input, ds-textarea, ds-select, ds-date-picker, ds-time-picker and ds-radio-group through a shared mixin. Defaults equal the values ds-input, ds-textarea, ds-select, ds-date-picker and ds-time-picker hard-coded, so those do not move; ds-radio-group's label moves from medium/s on the flat line height to bold/xs on the base one (its own item above). There is deliberately no per-component token set - custom-property scoping already narrows a retune to one element (`ds-select { --ds-field-label-transform: uppercase; }`) - and -transform/-tracking make the uppercase tracked label reachable through tokens for the first time. ds-input's --ds-input-label-color/-fs/-fw still take precedence where set and now fall through to the family token rather than the raw scale.",
|
|
275
|
+
"`--ds-field-height` is new, and the --field-h-sm/-md/-lg scale is now actually read by ds-input, ds-select, ds-date-picker and ds-time-picker - previously only -lg was, the other two sizes reaching past the scale to the raw --hit-min/--hit-cozy. Values are identical, so no height moves on upgrade while [data-density] sits on the root element; under a [data-density] set on an inner element, md and sm fields now keep the root's height, because the scale resolves on :root. NO ACTION, but two things become possible that silently did nothing before: retuning --field-h-md (or -sm) now moves every field, and --ds-field-height pins one height regardless of the size class, scopable per component. NOT a fix for unequal picker heights - those were already equal as of 0.7.1's aligned trigger geometry.",
|
|
228
276
|
"ds-button gained --ds-button-font-size / -weight / -tracking / -height / -pad-x / -pad-y, and reflects data-variant / data-color on its host element for external targeting. Defaults equal the hard-coded values, so nothing moves. NO ACTION - but a consumer who wrote .button.button.button { font-size; font-weight; letter-spacing; padding; height } to out-rank the shimmed .button.md can replace it with the tokens, set on the host. Per-variant --ds-button-* values were ALREADY reachable from the host before this change (the colour/fill resolvers read the hook first and never declare it), so an indirection layer added to work around that can go too.",
|
|
229
277
|
"ds-app-layout gained opt-in restoreScroll + restoreScrollTimeout, and LayoutScrollService gained contentReady() and consumePendingOffset(). Off by default, so NO ACTION. Turn it on for a list-and-details app and going back returns the reader to their place; forward links still land at the top. A 'back to list' control that adds a history entry instead of traversing must pass state: { dsRestoreScroll: true } to be restored. Note that an app which scrolls on navigation itself (an anchor jump, a URL that names a section) writes after the layout and wins, so restoreScroll is a no-op on those routes.",
|
|
230
278
|
"New role layer between the foundation scales and components: --ds-radius-{inner,control,panel,pill}, --ds-elevation-{raised,overlay,floating,modal}, and --ds-motion-{enter-panel,enter-surface,enter-large,exit,exit-large}-{duration,easing}. Every role defaults to the value its members already used, so NO ACTION and nothing moves visually. What becomes possible: retune one family without hitting the others - re-round panels while buttons keep their radius, lift every overlay in one line, make panel entrances snappier once. The old --shadow-popover/-modal/-toast/-card aliases still work and now resolve THROUGH the elevation roles. A per-component --ds-<comp>-radius / -shadow / -enter-duration override still wins over its role. Note: two motion resolvers (ds-loading-overlay, the toast leave) deliberately stay on the raw scale because they use --ease-standard, which no role carries.",
|
package/migrations/0.9.0.json
CHANGED
|
@@ -4,12 +4,12 @@
|
|
|
4
4
|
{
|
|
5
5
|
"id": "leave-keyframes-renamed",
|
|
6
6
|
"kind": "token-rename",
|
|
7
|
-
"old": "modal-out / ds-sheet-down / ds-sheet-fade-out / drawer-panel-close-right
|
|
8
|
-
"new": "ds-fade-out / ds-
|
|
7
|
+
"old": "modal-out / ds-sheet-down / ds-sheet-fade-out / drawer-panel-close-right / drawer-panel-close-left / drawer-panel-close-top / drawer-panel-close-bottom / drawer-scrim-out",
|
|
8
|
+
"new": "ds-fade-out / ds-slide-edge-out / ds-fade-out / ds-slide-edge-out / ds-slide-edge-out / ds-slide-edge-out / ds-slide-edge-out / ds-fade-out",
|
|
9
9
|
"action": "Only if you referenced an old name from a GLOBAL stylesheet: `modal-out`, `ds-sheet-fade-out` and `drawer-scrim-out` map to `ds-fade-out`; `ds-sheet-down` and all four `drawer-panel-close-*` map to `ds-slide-edge-out`. After upgrading, open and close a modal, a drawer and a bottom sheet and confirm the page scrolls again afterwards.",
|
|
10
10
|
"appliesWhen": "The old names were view-encapsulated, so only a global stylesheet could ever have referenced them. You also gain `--ds-modal-leave-keyframes`, `--ds-drawer-leave-keyframes` and `--ds-bottom-sheet-leave-keyframes`, the exit counterparts of the enter hooks.",
|
|
11
11
|
"pitfall": "Point a leave hook at your own GLOBAL `@keyframes` only — Angular renames a component-scoped animation name, so a scoped one never resolves. And check the scroll after closing: teardown used to match the animation NAME on animationend, and a teardown that does not fire leaks the body-scroll lock. That is the failure this change could cause and the one it was tested for.",
|
|
12
|
-
"note": "
|
|
12
|
+
"note": "Eight exit keyframes local to modal, drawer and bottom-sheet became four global presets mirroring the entrance vocabulary. The animationend guard checks the event came from the animated element rather than a child now, which is what freed the name. An exit preset reads `--_ds-exit-x/y/scale` and falls back to the matching enter values, so a surface that leaves the way it arrived declares nothing.",
|
|
13
13
|
"searchHints": [
|
|
14
14
|
"modal-out",
|
|
15
15
|
"ds-sheet-down",
|
|
@@ -18,7 +18,7 @@
|
|
|
18
18
|
"ds-sheet-fade-out"
|
|
19
19
|
],
|
|
20
20
|
"surface": "style",
|
|
21
|
-
"verify": "No global stylesheet names one of the
|
|
21
|
+
"verify": "No global stylesheet names one of the eight removed exit keyframes, and any --ds-*-leave-keyframes points at a GLOBAL @keyframes (a component-scoped name is renamed by Angular and will not resolve)."
|
|
22
22
|
},
|
|
23
23
|
{
|
|
24
24
|
"id": "dropdown-panel-radius",
|
|
@@ -45,7 +45,7 @@
|
|
|
45
45
|
"old": "ds-auth-shell",
|
|
46
46
|
"new": "ds-auth-layout",
|
|
47
47
|
"action": "Rename the element and its closing tag from `ds-auth-shell` to `ds-auth-layout`, and any stylesheet rule that names the element with it, then apply the class and token items below.",
|
|
48
|
-
"appliesWhen": "
|
|
48
|
+
"appliesWhen": "Every existing input and slot keeps its name - `brand`, `logoLetter`, `tagline`, `cardElevation`, `cardPadding`, `[brand]`, `[dsBrandName]`, `dsAuthSupport`; the same release adds `landmark` and short-viewport compression (informational below).",
|
|
49
49
|
"note": "\"Shell\" is not this library's word for a layout: the app-level one became ds-app-layout in 0.7.0, and calling the auth counterpart a shell put the split vocabulary back. It shipped as ds-auth-shell in exactly one release.",
|
|
50
50
|
"searchHints": [
|
|
51
51
|
"ds-auth-shell"
|
|
@@ -61,7 +61,7 @@
|
|
|
61
61
|
"old": "AuthShellComponent",
|
|
62
62
|
"new": "AuthLayoutComponent",
|
|
63
63
|
"action": "Replace `AuthShellComponent` with `AuthLayoutComponent` in imports and type references.",
|
|
64
|
-
"note": "The exported class follows the selector rename
|
|
64
|
+
"note": "The exported class follows the selector rename; it also gained the `landmark` input and a protected `markGlyph`.",
|
|
65
65
|
"searchHints": [
|
|
66
66
|
"AuthShellComponent"
|
|
67
67
|
],
|
|
@@ -75,7 +75,7 @@
|
|
|
75
75
|
"action": "Replace the prefix `--ds-auth-shell-` with `--ds-auth-layout-` on the six component tokens: `-min-height`, `-card-max-width`, `-gap`, `-bg-color`, `-mark-bg-color`, `-mark-label-color`.",
|
|
76
76
|
"appliesWhen": "DS-owned tokens only — no others ship under this prefix, and a variable of your own is out of scope.",
|
|
77
77
|
"pitfall": "Do NOT rename `--auth-card-w`. It is the global scale token behind `-card-max-width`, it carries no `--ds-auth-shell-` prefix, and it keeps its name — a prefix-blind sweep that catches it breaks the fallback.",
|
|
78
|
-
"note": "Values
|
|
78
|
+
"note": "Values are unchanged; the -gap default now clamps against svh (informational: short-viewport compression).",
|
|
79
79
|
"searchHints": [
|
|
80
80
|
"--ds-auth-shell-"
|
|
81
81
|
],
|
|
@@ -87,7 +87,7 @@
|
|
|
87
87
|
"old": "ds-search",
|
|
88
88
|
"new": null,
|
|
89
89
|
"action": "None unless you want the old height: `ds-search { --ds-search-height: 36px; }` — that token still wins over everything.",
|
|
90
|
-
"appliesWhen": "sm (32px) and lg (48px) are unchanged; only the md default moved. The height also falls through `--ds-field-height` now, so `--ds-field-height: 44px` on a toolbar levels search along with the fields.",
|
|
90
|
+
"appliesWhen": "sm (32px) and lg (48px) are unchanged; only the md default moved. Under a [data-density=\"ultra-compact\"] set on an inner container rather than the root, sm now stays 32px where it followed --hit-min to 24px. The height also falls through `--ds-field-height` now, so `--ds-field-height: 44px` on a toolbar levels search along with the fields.",
|
|
91
91
|
"note": "ds-search is 40px at the default size, was 36px. The old 36px was a lone tier nothing else used, while ds-button, ds-input, ds-select and both pickers all resolve `--field-h-md`, so a search box in a toolbar sat 4px short of every neighbour.",
|
|
92
92
|
"searchHints": [
|
|
93
93
|
"ds-search",
|
|
@@ -146,7 +146,7 @@
|
|
|
146
146
|
"old": "ds-number-stepper",
|
|
147
147
|
"new": null,
|
|
148
148
|
"action": "None unless you want the old height: `ds-number-stepper { --ds-field-height: 44px; }` scoped to the instance, or set the size back to md.",
|
|
149
|
-
"appliesWhen": "One size only — sm (32px) and the md default (40px) are unchanged.",
|
|
149
|
+
"appliesWhen": "One size only — sm (32px) and the md default (40px) are unchanged. Under a [data-density] set on an inner container rather than the root, sm and md now keep the root height instead of following that container's --hit-min / --hit-cozy.",
|
|
150
150
|
"note": "`size=\"lg\"` is 48px, was 44px: it resolved `--hit-comfy` while the family's large size is `--field-h-lg`, so a large stepper was a step short of a large input beside it. The +/- buttons and the quantity box derive their widths from that height, so they widen with it.",
|
|
151
151
|
"searchHints": [
|
|
152
152
|
"ds-number-stepper",
|
|
@@ -169,14 +169,14 @@
|
|
|
169
169
|
"kind": "code-add",
|
|
170
170
|
"old": "ds-tabs",
|
|
171
171
|
"new": "urlParam=\"tab\"",
|
|
172
|
-
"action": "Per strip, and worth a deliberate pass. (1) Give each `ds-tab` a `value` if it has none. (2) Use one strip per parameter name — nested or sibling strips need distinct names, such as `tab` and `subtab`. (3) Delete any hand-rolled wiring: a queryParamMap subscription plus a `navigate()` on `
|
|
172
|
+
"action": "Per strip, and worth a deliberate pass. (1) Give each `ds-tab` a `value` if it has none. (2) Use one strip per parameter name — nested or sibling strips need distinct names, such as `tab` and `subtab`. (3) Delete any hand-rolled wiring: a queryParamMap subscription plus a `navigate()` on `(selectedIndexChange)` is exactly what this replaces.",
|
|
173
173
|
"appliesWhen": "Nothing changes until you set `urlParam`.",
|
|
174
174
|
"pitfall": "Two traps, both silent until someone shares a link. Without a `value` the URL is written from the LABEL, so the link breaks the moment the label is translated or reworded. And two strips sharing a parameter name erase each other — both write the same query parameter and a reload restores whichever wrote last. A dev-mode warning names that clash.",
|
|
175
175
|
"note": "Setting `urlParam=\"tab\"` makes the strip write `?tab=<name>`, so the active tab survives F5, a shared link and the Back button.",
|
|
176
176
|
"searchHints": [
|
|
177
177
|
"<ds-tabs",
|
|
178
178
|
"ds-tabs",
|
|
179
|
-
"
|
|
179
|
+
"selectedIndexChange",
|
|
180
180
|
"queryParamMap"
|
|
181
181
|
],
|
|
182
182
|
"surface": [
|
|
@@ -196,9 +196,9 @@
|
|
|
196
196
|
"old": "extends TableComponent",
|
|
197
197
|
"new": null,
|
|
198
198
|
"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.",
|
|
199
|
-
"appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (
|
|
200
|
-
"pitfall": "
|
|
201
|
-
"note": "Seventeen classes
|
|
199
|
+
"appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (components.md § Components); template users need nothing.",
|
|
200
|
+
"pitfall": "One thing 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. The private `distinctValuesOf()` was replaced by a private `optionsFor()`: a subclass that declared its own `distinctValuesOf` no longer collides, and one declaring `optionsFor` now does (TS2415). Also note both CVA bases gained a `focus()` inherited by every field control, so a subclass with its own needs `override`, and nine new exported symbols can shadow a local name: AuthLayoutComponent, FieldGroupComponent, DS_FIELD_GROUP, DsFieldGroupContext, DsScrollReset, HeaderFilterDirective, HeaderFilterContext, TableFilterMode, LayoutNavigationService — none of these was exported at 0.8.0, so they are new exports rather than grown classes.",
|
|
201
|
+
"note": "Seventeen classes declare a new member, and eight more inherit three from the CVA bases. 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. `CheckboxComponent`, `ColorPickerComponent`, `MultiSelectComponent`, `OtpInputComponent`, `RadioGroupComponent`, `SliderComponent`, `SwitchComponent` and `TimePickerComponent` each gained `focus`, `hidden` and `hostElement`. `AutocompleteComponent` gained 9. `InputComponent` gained 8. `TextareaComponent` gained 7. `SelectComponent` gained 6. `DatePickerComponent` gained 4. `TableComponent` gained 30 and lost `distinctValuesOf`. `TabsComponent` gained 8. `AppLayoutComponent` gained `scrollReset`, `MenuItemComponent` `quiet`, `BreadcrumbsComponent` `allItems` and `maxItems`, `LayoutScrollService` `configureReset` and `resetStrategy`, `ModalComponent` and `ModalCardComponent` `dividers` and `subtitle`.",
|
|
202
202
|
"searchHints": [
|
|
203
203
|
"extends TableComponent",
|
|
204
204
|
"extends InputComponent",
|
|
@@ -222,7 +222,51 @@
|
|
|
222
222
|
"detect": [
|
|
223
223
|
"extends TableComponent",
|
|
224
224
|
"extends ",
|
|
225
|
-
"override "
|
|
225
|
+
"override ",
|
|
226
|
+
"extends AppLayoutComponent",
|
|
227
|
+
"AppLayoutComponent",
|
|
228
|
+
"extends AutocompleteComponent",
|
|
229
|
+
"AutocompleteComponent",
|
|
230
|
+
"extends BreadcrumbsComponent",
|
|
231
|
+
"BreadcrumbsComponent",
|
|
232
|
+
"extends ButtonComponent",
|
|
233
|
+
"ButtonComponent",
|
|
234
|
+
"extends CheckboxComponent",
|
|
235
|
+
"CheckboxComponent",
|
|
236
|
+
"extends ColorPickerComponent",
|
|
237
|
+
"ColorPickerComponent",
|
|
238
|
+
"extends DatePickerComponent",
|
|
239
|
+
"DatePickerComponent",
|
|
240
|
+
"extends InputComponent",
|
|
241
|
+
"InputComponent",
|
|
242
|
+
"extends LayoutScrollService",
|
|
243
|
+
"LayoutScrollService",
|
|
244
|
+
"extends MenuItemComponent",
|
|
245
|
+
"MenuItemComponent",
|
|
246
|
+
"extends ModalCardComponent",
|
|
247
|
+
"ModalCardComponent",
|
|
248
|
+
"extends ModalComponent",
|
|
249
|
+
"ModalComponent",
|
|
250
|
+
"extends MultiSelectComponent",
|
|
251
|
+
"MultiSelectComponent",
|
|
252
|
+
"extends OtpInputComponent",
|
|
253
|
+
"OtpInputComponent",
|
|
254
|
+
"extends RadioGroupComponent",
|
|
255
|
+
"RadioGroupComponent",
|
|
256
|
+
"extends SearchComponent",
|
|
257
|
+
"SearchComponent",
|
|
258
|
+
"extends SelectComponent",
|
|
259
|
+
"SelectComponent",
|
|
260
|
+
"extends SliderComponent",
|
|
261
|
+
"SliderComponent",
|
|
262
|
+
"extends SwitchComponent",
|
|
263
|
+
"SwitchComponent",
|
|
264
|
+
"extends TabsComponent",
|
|
265
|
+
"TabsComponent",
|
|
266
|
+
"extends TextareaComponent",
|
|
267
|
+
"TextareaComponent",
|
|
268
|
+
"extends TimePickerComponent",
|
|
269
|
+
"TimePickerComponent"
|
|
226
270
|
],
|
|
227
271
|
"verify": "A typecheck reports no TS4114 / TS2415 / TS2416 on any class extending a DS component; a subclass that overrode isStriped() reads an ABSOLUTE row index now."
|
|
228
272
|
},
|
|
@@ -256,27 +300,27 @@
|
|
|
256
300
|
}
|
|
257
301
|
],
|
|
258
302
|
"informational": [
|
|
259
|
-
"--ds-radius-inner now actually reaches the small affordances. 33 reads across fifteen component stylesheets took var(--radius-sm) directly - dropdown options, field clear buttons, calendar days, chips, tag and toast close buttons - so the role a consumer is told to retune reached exactly one component. They resolve the role now, and its default IS --radius-sm, so NOTHING MOVES. NO ACTION, but it changes what a square brand costs you: zeroing the three roles
|
|
260
|
-
"A 32px toolbar is `density=\"compact\"`, not a per-control height pin. Measured on a nine-control row: search, input, select, autocomplete, date-picker, time-picker, multi-select, number-stepper and button are all 40px by default and all 32px under [data-density=\"compact\"] on the container. DELETE-LIST MATERIAL: if you pin --ds-search-height, or reach past it to --hit-min, to get a shorter row - that pin can go, and after the height contract it was fighting the family rather than joining it. `--hit-min` is also a legitimate density knob, so discard hits where it is set deliberately rather than to shorten a search row. Known limit at the bottom of the scale: ds-multi-select and ds-autocomplete hold chips, so they set a min-height rather than a height and stop following the floor once it drops below what the text needs - under ultra-compact they are 33px and 29px where the rest reach 24px, because a density tier scales padding and hit targets but not the type scale. Compact is unaffected in practice (33 against 32). Documented on the Density page. (delete list: search-height-pinned-for-a-short-row)",
|
|
303
|
+
"--ds-radius-inner now actually reaches the small affordances. 33 reads across fifteen component stylesheets took var(--radius-sm) directly - dropdown options, field clear buttons, calendar days, chips, tag and toast close buttons - so the role a consumer is told to retune reached exactly one component. They resolve the role now, and its default IS --radius-sm, so NOTHING MOVES. NO ACTION, but it changes what a square brand costs you: zeroing the three roles now squares these affordances too, while surfaces that still read the raw scale - the ds-multi-select panel, menus and steppers among them - stay rounded. Two deliberate exclusions - five focus-ring radii inside :focus-visible keep following the raw scale (a ring traces a box, it is not a brand surface), and the ds-multi-select and ds-color-picker panels, each its own element, and the ds-menu host still hard-code --radius-md (8px), where the ds-select, ds-autocomplete, ds-date-picker, ds-time-picker and ds-popover panels resolve --ds-radius-panel (12px). That last one is a known inconsistency, not a hook: squaring it needs the scale. Worked example on the Theming page.",
|
|
304
|
+
"A 32px toolbar is `density=\"compact\"`, not a per-control height pin. Measured on a nine-control row: search, input, select, autocomplete, date-picker, time-picker, multi-select, number-stepper and button are all 40px by default and all 32px under [data-density=\"compact\"] on the root element. Not on an inner container: their heights read `--field-h-*`, which resolve once on `:root`, so the attribute lower down leaves them at 40px. DELETE-LIST MATERIAL: if you pin --ds-search-height, or reach past it to --hit-min, to get a shorter row - that pin can go, and after the height contract it was fighting the family rather than joining it. `--hit-min` is also a legitimate density knob, so discard hits where it is set deliberately rather than to shorten a search row. Known limit at the bottom of the scale: ds-multi-select and ds-autocomplete hold chips, so they set a min-height rather than a height and stop following the floor once it drops below what the text needs - under ultra-compact they are 33px and 29px where the rest reach 24px, because a density tier scales padding and hit targets but not the type scale. Compact is unaffected in practice (33 against 32). Documented on the Density page. (delete list: search-height-pinned-for-a-short-row)",
|
|
261
305
|
"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.",
|
|
262
306
|
"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. Setting it transparent leaves the header and actions padding sized to clear a rule that is no longer drawn, stacking into a 35px gap where 16px was wanted. [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. (delete list: modal-divider-transparent-plus-padding)",
|
|
263
307
|
"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 header that has to carry `title + ds-badge` over a second line used to be a reason to drop ds-modal and re-implement the scrim, the body scroll lock, backdrop-click and Escape by hand - which costs the focus trap, focus restore, the enter/leave animation and, easily, the footer, leaving 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.",
|
|
264
308
|
"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.",
|
|
265
309
|
"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.",
|
|
266
|
-
"--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 (delete list: field-height-pin-on-late-adopters).",
|
|
310
|
+
"--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), with [data-density] on the root element; under a [data-density] set on an inner container the --field-h-* scale keeps its root value, so these six no longer follow that container's density. NO ACTION unless you had already worked around the gap by pinning height on one of these - that pin can go (delete list: field-height-pin-on-late-adopters).",
|
|
267
311
|
"The six connected panels (ds-select, ds-multi-select, ds-autocomplete, ds-color-picker, ds-date-picker, ds-time-picker) now build their overlay from one shared helper instead of six identical copies. Internal only, NO ACTION: the position, the 4px gap, the flip-above fallback, the panel classes and the scroll strategy are byte-for-byte what they were.",
|
|
268
312
|
"ds-autocomplete gained dsAutocompletePrefix / dsAutocompleteSuffix content slots and [showChevron] (default true). Additive, NO ACTION. If you absolutely positioned a search glyph over the field and re-padded the input, or hid the arrow with a global rule reaching for .autocomplete-chevron, replace both: put the icon in the prefix slot and set [showChevron]=\"false\". The slot names and behaviour match ds-input's dsInputPrefix / dsInputSuffix.",
|
|
269
313
|
"ds-autocomplete gained a public clear() that empties the value AND the typed text. If you reset the field by querying the inner <input> out of the DS's DOM and dispatching a synthetic input event, delete that and call clear() on a viewChild ref - the DOM shape it depended on is not part of the public API. It deliberately does not move focus. (delete list: autocomplete-synthetic-input-clear)",
|
|
270
|
-
"ds-autocomplete gained --ds-autocomplete-panel-radius (default --ds-radius-panel) and --ds-autocomplete-panel-maxh (default --picker-maxh). NO ACTION - both defaults equal today's values. The radius one matters if you square the radius roles: the autocomplete panel
|
|
271
|
-
"ds-table gained --ds-table-head-pad-top / --ds-table-head-pad-bottom, plus showPageSize and showLabel forwarded to its footer pager. All additive with today's values as defaults, NO ACTION. Separately FIXED: density=\"compact\" pinned padding onto the cells, which out-specified every --ds-table-*-pad-* hook, so a compact table silently ignored all of them; it now retunes the density tokens instead. Spacing is unchanged - but if you fought that with an !important, it can go. (delete list: compact-cell-padding-important)",
|
|
314
|
+
"ds-autocomplete gained --ds-autocomplete-panel-radius (default --ds-radius-panel) and --ds-autocomplete-panel-maxh (default --picker-maxh). NO ACTION - both defaults equal today's values. The radius one matters if you square the radius roles: the autocomplete panel hard-coded --radius-lg, so it stayed rounded when the roles were squared. The max-height one replaces reaching for the private --picker-maxh, which ds-multi-select also reads.",
|
|
315
|
+
"ds-table gained --ds-table-head-pad-top / --ds-table-head-pad-bottom, plus showPageSize and showLabel forwarded to its footer pager. All additive with today's values as defaults, NO ACTION. Separately FIXED: density=\"compact\" pinned padding onto the cells, which out-specified every --ds-table-*-pad-* hook, so a compact table silently ignored all of them; it now retunes the density tokens instead. Spacing is unchanged except the empty-state cell, which keeps its own 16px padding where compact gave it 8px 12px - but if you fought that with an !important, it can go. (delete list: compact-cell-padding-important)",
|
|
272
316
|
"ds-date-picker and ds-time-picker resolve their trigger's horizontal padding from --field-pad-x (new hooks: --ds-date-picker-trigger-pad-x, --ds-time-picker-trigger-pad-x) instead of a hard-coded --space-3. Identical at the default density; the difference shows under [data-density], where the token shrinks and the literal did not, leaving a picker 8px wider than the input beside it. NO ACTION unless you hand-pinned picker padding to compensate.",
|
|
273
|
-
"The ds-auth-shell -> ds-auth-layout rename
|
|
317
|
+
"The ds-auth-shell -> ds-auth-layout rename itself changes only names; the same release also adds `landmark`, four tokens and short-viewport compression (entries below). If you never adopted ds-auth-shell (added in 0.8.0), there is nothing to do.",
|
|
274
318
|
"FIXED in ds-textarea: size=\"sm\" and size=\"lg\" rendered the md vertical padding (12px top and bottom) regardless of the size. The size blocks set the inner textarea's vertical pad, but a :host-prefixed pin at the end of the file out-ranked them once emulated encapsulation shimmed both selectors - it carries one more attribute than the size selector. There are now three pins, one per size, and the size blocks keep only the horizontal padding they own. NO ACTION: the change is visible only on a non-md textarea and the md default is unchanged. Note that retuning --ds-input-pad-y previously moved all three sizes together; if you compensated for the wrong padding with your own override on a sm or lg textarea, that override now stacks on the corrected value and can go (delete list: textarea-size-padding-compensation).",
|
|
275
319
|
"ds-auth-layout now COMPRESSES its own chrome on a short viewport: block padding, the column gap, the letter-mark tile and the masthead inner gap clamp against svh. No action - behaviour only, and a viewport 800px tall or more renders exactly what it did before. Read that as a VIEWPORT height, not a screen size: a 1366x768 laptop sits near 630px after browser and OS chrome, and a 1080p screen at 150% display scaling near 585px, so plenty of desktops do get the compressed furniture. Type is deliberately NOT clamped: the wordmark and the tile's glyph were measured to buy zero vertical space (the tile sets the row height at every viewport, and the glyph sits in a fixed-size box) while flattening the brand against a fixed 14px tagline, so both keep the fixed sizes 0.8.0 ships. Below 800px the remaining furniture shrinks so it is not what pushes a card into scrolling (~131px instead of ~219px at a landscape phone's ~330px). Two tokens opt out per dimension: --ds-auth-layout-pad-block and --ds-auth-layout-mark-size; setting any of those or the existing --ds-auth-layout-gap to a fixed value stops that one compressing. A card taller than the remaining space still scrolls - that is intended.",
|
|
276
320
|
"ds-auth-layout audit fixes, all additive or corrective - NO ACTION. The letter-mark tile is now aria-hidden (a screen reader announced 'A MyAdmin', now 'MyAdmin') and carries flex-shrink: 0 so a long wordmark cannot squash it out of square; logoLetter on its own renders its tile instead of nothing; the glyph is taken by code point rather than charAt(0), which returned half a surrogate pair for a brand starting with an emoji; box-sizing: border-box is declared on the host rather than inherited, so the component still avoids its own overflow scrollbar for a consumer composing style partials without styles/reset. The four env(safe-area-inset-*) calls gained 0px fallbacks and moved to physical padding-left/padding-right so the insets cannot swap sides under RTL - and note they are inert unless YOUR app sets viewport-fit=cover in its viewport meta, which the library cannot set for you. New tokens, both defaulting to today's behaviour: --ds-auth-layout-mark-radius (the tile's radius was the one value with no override hop) and --ds-auth-layout-brand-max-height (none by default; set it to cap a projected [brand] logo, which nothing constrained). New input landmark, default 'none': set landmark=\"main\" on a standalone auth page so the card - an <article>, which is not a landmark - becomes something a screen-reader user can jump to; it stays opt-in because this layout is also embedded inside pages that already own a main.",
|
|
277
321
|
"ds-icon now logs a dev-mode warning when an icon name is in neither the DS set nor your provideDsIcons() registry - previously it rendered an empty <svg> silently. No action, and nothing changes in production. Expect the warning to surface real typos the moment you upgrade.",
|
|
278
322
|
"ds-app-layout gained scrollReset: \"path\" | \"never\" | \"always\" (default \"path\" = existing behaviour, so NO ACTION), and LayoutNavigationService is now exported. If you wrote your own \"did the path change?\" check to work around the layout resetting scroll - or to skip a view transition, or to reset a tab - replace it with inject(LayoutNavigationService).pathChanged: it is NavigationEnd, path only, de-duplicated, and it skips a navigation carrying state: { dsSamePage: true }. Note a naive split(\"?\") is NOT equivalent, it keeps the fragment this stream strips. To stop the layout resetting scroll on a paged or filtered list, set scrollReset=\"never\" and call LayoutScrollService.scrollToTop() where you actually want it.",
|
|
279
|
-
"Options in ds-select / ds-
|
|
323
|
+
"Options in ds-select / ds-multi-select panels now have a pressed state (they had hover only, which does nothing on touch); ds-autocomplete styles its own rows and still has hover only. No action - visual only. If you styled :active on .option yourself to work around it, you can drop that override; if you want a different pressed fill, it reads --surface-muted (neutral rows) and --primary-subtitle (the selected row). (delete list: dropdown-option-active-override)",
|
|
280
324
|
"ds-table gained filterMode: \"client\" | \"server\" | \"none\" and columnFilterOptions. It resolves to \"server\" when unset - see the table-sort-filter-mode-default-server item, which is where the action for that lives. If your table is server-paged (you bind `total`) and any column has filter: \"set\", you WANT filterMode=\"server\" plus columnFilterOptions with the real value domain - otherwise the checklist offers only the values on the current page and then filters locally on top of the server. A dev warning now points this out.",
|
|
281
325
|
"ds-table gained dsHeaderFilter, a template slot for a header filter the built-in checklist cannot express (date range, numeric threshold, async options). Additive, NO ACTION. If you built a host-owned popover outside the table for this, you can move it inside: <ng-template dsHeaderFilter=\"key\" [active]=\"...\" let-close=\"close\">. The table keeps the button, the popover and the active styling; `active` is how you tell it your criterion is set, and `close` dismisses the panel after applying. A projected filter also makes the column filterable on its own - you do not additionally need filter: \"set\".",
|
|
282
326
|
"ds-table now announces sort state and row range through its role=\"status\" region (\"Sorted by Owner, ascending\", \"Showing 1-25 of 240\"). No action - it is additive and the first render stays silent, since aria-live announces changes rather than initial content. If you added your own live region around the table for this, remove it or you will get double announcements. Wording is overridable per table through the sortAnnouncement and rangeAnnouncement inputs, which take the facts and return the sentence. (delete list: table-own-live-region)",
|
|
@@ -386,7 +430,7 @@
|
|
|
386
430
|
"-radius: 0"
|
|
387
431
|
],
|
|
388
432
|
"why": "A dozen scattered `--ds-*-radius: 0`",
|
|
389
|
-
"replaceWith": "For a fully square brand, four lines: `--radius-sm/md/lg/xl: 0` (leave `--radius-pill`).
|
|
433
|
+
"replaceWith": "For a fully square brand, four lines: `--radius-sm/md/lg/xl: 0` (leave `--radius-pill`). The radius roles alone leave the multi-select panel, menus, steppers and other surfaces that still read the raw scale rounded; they are the tool for squaring one family and keeping another. Worked example on the Theming page"
|
|
390
434
|
},
|
|
391
435
|
{
|
|
392
436
|
"id": "overlay-pane-squared-globally",
|
|
@@ -517,10 +561,9 @@
|
|
|
517
561
|
".option",
|
|
518
562
|
":active",
|
|
519
563
|
"ds-select",
|
|
520
|
-
"ds-autocomplete",
|
|
521
564
|
"ds-multi-select"
|
|
522
565
|
],
|
|
523
|
-
"why": "An :active rule you wrote on a panel option because the options had hover only, which does nothing on touch.
|
|
566
|
+
"why": "An :active rule you wrote on a ds-select or ds-multi-select panel option because the options had hover only, which does nothing on touch. Those two paint a pressed state themselves now; ds-autocomplete styles its own rows and still has none, so an :active rule on its options stays.",
|
|
524
567
|
"replaceWith": "nothing - or retune it through --surface-muted and --primary-subtitle"
|
|
525
568
|
},
|
|
526
569
|
{
|
package/migrations/0.9.1.json
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
"informational": [
|
|
5
5
|
"Nothing in this release changes the package's runtime. The entire change is documentation, feeding the token and component reference; every component behaves exactly as it did on 0.9.0.",
|
|
6
6
|
"THREE behaviours are easy to guess wrong, so check these if you use them - the code has always worked this way. (1) ds-time-columns `value` is always HH:mm in 24h and `format` changes only the DISPLAY, so a picker showing 12h still emits 24h - code that parsed the emitted value as 12h was wrong. (2) ds-time-columns `minTime`/`maxTime` DISABLE the out-of-range rows rather than removing them, so the columns keep their height as a bound moves - a layout that assumed the list shortens was wrong. (3) ds-calendar-day `tabIndex` is a roving tabindex owned by the grid (exactly one cell at 0, the rest at -1), not a tab position to set per day - setting it per cell fights the grid's keyboard model.",
|
|
7
|
-
"41 public tokens and props gained descriptions in the reference: 10 --ds-*
|
|
7
|
+
"41 public tokens and props gained descriptions in the reference: 10 tokens (nine --ds-* - the whole --ds-password-rules-* set, --ds-multi-select-panel-bg-color and --ds-menu-item-radius among them - plus the global --auth-card-w) and 31 inputs and outputs across ds-calendar-day, ds-time-columns, ds-field-message, ds-divider, ds-sidenav-footer and the three layout primitives. Names, types and defaults are unchanged.",
|
|
8
8
|
"A release manifest carries a deleteList wherever that release made a workaround unnecessary, so an upgrade tool can act on what became redundant and not only on what broke. Each row is machine-readable: { id, surface, find, why, replaceWith }."
|
|
9
9
|
],
|
|
10
10
|
"deleteList": []
|
package/migrations/README.md
CHANGED
|
@@ -12,12 +12,13 @@ One file per released version — `migrations/<version>.json` — mirroring that
|
|
|
12
12
|
"detect": ["<shape written the way the CONSUMER writes it>", "..."],
|
|
13
13
|
"verify": "<the positive assertion that proves this landed>",
|
|
14
14
|
"restore": "<literal snippet that brings the old behaviour back | null>",
|
|
15
|
-
"supersedes": ["<version>#<id>"]
|
|
15
|
+
"supersedes": ["<version>#<id>"],
|
|
16
|
+
"evidence": ["commit:<sha> | fixture:<path> | pixels:<block id> | tokens:<name> | command:<shell>"] } ],
|
|
16
17
|
"deleteList": [ { "id": "<slug>", "surface": "<surface>", "find": ["<shape>", "..."],
|
|
17
18
|
"why": "<what made it unnecessary>",
|
|
18
19
|
"replaceWith": "<the API that replaces it>" } ],
|
|
19
20
|
"informational": [ "<one-line FYI per non-actionable change group>" |
|
|
20
|
-
{ "text": "...", "verify": "<one concrete eyeball check>" } ] }
|
|
21
|
+
{ "text": "...", "verify": "<one concrete eyeball check>", "evidence": ["..."] } ] }
|
|
21
22
|
```
|
|
22
23
|
|
|
23
24
|
- `kind` ∈ `selector-rename | type-rename | input-rename | output-rename | token-rename |
|
|
@@ -50,10 +51,16 @@ One file per released version — `migrations/<version>.json` — mirroring that
|
|
|
50
51
|
affected, so an item can be ruled out without searching.
|
|
51
52
|
- **`pitfall`** — the way to apply the item mechanically correctly and still ship a broken app.
|
|
52
53
|
Read it before deciding a clean build means done.
|
|
54
|
+
- **`evidence`** - what measured the outcome the entry's prose asserts: that rendering or behaviour
|
|
55
|
+
did not change, a compile outcome, or a count of things. `commit:<sha>` inside the boundary the
|
|
56
|
+
manifest describes, `fixture:<path>` under `migrations/fixtures/`, `pixels:<docs block id>`
|
|
57
|
+
(`<section anchor>/<chapter slug>`, such as `button/sizes`, whose pixels did not change across
|
|
58
|
+
the boundary), `tokens:<token name>`, or `command:<shell command>`. Optional on an item and on an object-form
|
|
59
|
+
`informational` entry, and required wherever the prose makes such a claim.
|
|
53
60
|
- **`deleteList`** — the structured form of "what you can now delete" (see below).
|
|
54
61
|
- **`informational`** — a non-actionable FYI, a bare string or `{ "text": "...", "verify": "..." }`
|
|
55
62
|
where `verify` is the one eyeball check for a change to rendering alone (no symbol for a grep or
|
|
56
|
-
a build to catch).
|
|
63
|
+
a build to catch); the object carries `evidence` when `text` asserts a measured outcome.
|
|
57
64
|
|
|
58
65
|
**Why:** an upgrade tool can read the plan out of the prose changelog, but it re-derives it on
|
|
59
66
|
every run. A shipped manifest makes it deterministic: the tool validates and prefers the
|
|
@@ -97,6 +104,53 @@ behaviour back. **Every published manifest meets this contract**, back to the ea
|
|
|
97
104
|
legacy tier and no warning level: `surface`, `detect`, `verify` and `restore` are present wherever
|
|
98
105
|
they apply.
|
|
99
106
|
|
|
107
|
+
**Compile fixtures.** A sentence that states a compile outcome - "fails with TS2416", "TS2353
|
|
108
|
+
inline, silent through a prebuilt object", "compiles but never runs" - is backed by
|
|
109
|
+
`migrations/fixtures/<version>/<id>.ts` (`unreleased/` for the draft), named by the item's or the
|
|
110
|
+
`deleteList` row's `id`, or `informational-<n>` for the n-th `informational` line, counted from 1
|
|
111
|
+
(an informational line has no id, so inserting one above renumbers the fixtures below it): consumer-side
|
|
112
|
+
TypeScript importing from `@ids-group-ltd/ids-design-system` and its secondary entry points, as an
|
|
113
|
+
app would. It is type-checked against the library source at both ends of the boundary, the
|
|
114
|
+
previous stable tag and this one, with `strict`, `noImplicitOverride` (the Angular CLI scaffolds
|
|
115
|
+
it, and it is what turns a new base member into TS4114) and `skipLibCheck`. A line expected to fail
|
|
116
|
+
carries a directive on the line above, naming the side and the exact codes:
|
|
117
|
+
|
|
118
|
+
```ts
|
|
119
|
+
// @ts-expect-error after TS2353 this release reports TS2353 here, the previous is clean
|
|
120
|
+
// @ts-expect-error before TS4114 the other way round: "compiles but never runs"
|
|
121
|
+
// @ts-expect-error both TS4114 TS2416 both report exactly these
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
The codes reported on a line must equal the codes named, and a line with no directive must compile
|
|
125
|
+
clean at both tags; TypeScript's own `@ts-expect-error` accepts any error, so the directive is
|
|
126
|
+
stripped before compiling. Every TS code, and every compile-time NG code (`NG1000` and up), an
|
|
127
|
+
item, a `deleteList` row or an `informational` line names must be one its fixture asserts. Fixtures
|
|
128
|
+
are kept in the repository and not shipped.
|
|
129
|
+
|
|
130
|
+
A template outcome is backed by `<id>.component.ts` instead: a standalone component importing what
|
|
131
|
+
it uses, its template inline in `template:`, compiled by the Angular compiler with
|
|
132
|
+
`strictTemplates`. A template line expected to fail carries the directive as an HTML comment on the
|
|
133
|
+
line above, with TS or NG codes, and the TypeScript part of the file takes `// @ts-expect-error`
|
|
134
|
+
as before:
|
|
135
|
+
|
|
136
|
+
```ts
|
|
137
|
+
template: `
|
|
138
|
+
<!-- expect: after NG8002 -->
|
|
139
|
+
<ds-accordion [multi]="false"></ds-accordion>
|
|
140
|
+
`,
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
An `.html` fixture is not compiled.
|
|
144
|
+
|
|
145
|
+
**Locator fixtures.** `migrations/fixtures/<version>/<id>.found.<ext>` holds consumer code an item
|
|
146
|
+
must locate, and `<id>.ignored.<ext>` a look-alike it must not count (the same attribute on another
|
|
147
|
+
element), `ext` being `html`, `ts` or `scss`. They are searched the way the usage finder searches: a
|
|
148
|
+
literal grep for `old` (the attribute of an `element[attr]`), every `searchHints` entry and every
|
|
149
|
+
`detect` shape, where a hit from `old` or a hint counts only inside the element `old` names, and a
|
|
150
|
+
`detect` hit is scoped the same way only on a template-only item. A `.found` snippet nothing locates
|
|
151
|
+
is a locator defect in the manifest, and an `.ignored` one a hit survives in is a scope defect.
|
|
152
|
+
Every item of the draft carries a `.found` fixture; they are kept in the repository and not shipped.
|
|
153
|
+
|
|
100
154
|
The prose CHANGELOG is the human copy of a release; the manifest is its machine mirror of the
|
|
101
155
|
same release. Where the two disagree, the CHANGELOG is the one to trust.
|
|
102
156
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ids-group-ltd/ids-design-system",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.15.0",
|
|
4
4
|
"description": "IDS Group Angular design system: components, tokens, themes",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"homepage": "https://ids-ds.proto.ids-group.co.uk/",
|
|
@@ -18,6 +18,8 @@
|
|
|
18
18
|
"./styles/*": "./styles/*",
|
|
19
19
|
"./themes/*": "./themes/*",
|
|
20
20
|
"./migrations/*": "./migrations/*",
|
|
21
|
+
"./stylelint": "./stylelint/index.mjs",
|
|
22
|
+
"./eslint": "./eslint/index.mjs",
|
|
21
23
|
"./package.json": {
|
|
22
24
|
"default": "./package.json"
|
|
23
25
|
},
|
|
@@ -129,6 +131,10 @@
|
|
|
129
131
|
"types": "./types/ids-group-ltd-ids-design-system-components-date-picker.d.ts",
|
|
130
132
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs"
|
|
131
133
|
},
|
|
134
|
+
"./components/definition-term": {
|
|
135
|
+
"types": "./types/ids-group-ltd-ids-design-system-components-definition-term.d.ts",
|
|
136
|
+
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs"
|
|
137
|
+
},
|
|
132
138
|
"./components/description-list": {
|
|
133
139
|
"types": "./types/ids-group-ltd-ids-design-system-components-description-list.d.ts",
|
|
134
140
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs"
|
|
@@ -173,6 +179,10 @@
|
|
|
173
179
|
"types": "./types/ids-group-ltd-ids-design-system-components-icon-button.d.ts",
|
|
174
180
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs"
|
|
175
181
|
},
|
|
182
|
+
"./components/info-hint": {
|
|
183
|
+
"types": "./types/ids-group-ltd-ids-design-system-components-info-hint.d.ts",
|
|
184
|
+
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs"
|
|
185
|
+
},
|
|
176
186
|
"./components/input": {
|
|
177
187
|
"types": "./types/ids-group-ltd-ids-design-system-components-input.d.ts",
|
|
178
188
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-input.mjs"
|
|
@@ -485,6 +495,10 @@
|
|
|
485
495
|
"types": "./types/ids-group-ltd-ids-design-system-components-date-picker.d.ts",
|
|
486
496
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs"
|
|
487
497
|
},
|
|
498
|
+
"./definition-term": {
|
|
499
|
+
"types": "./types/ids-group-ltd-ids-design-system-components-definition-term.d.ts",
|
|
500
|
+
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs"
|
|
501
|
+
},
|
|
488
502
|
"./description-list": {
|
|
489
503
|
"types": "./types/ids-group-ltd-ids-design-system-components-description-list.d.ts",
|
|
490
504
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs"
|
|
@@ -529,6 +543,10 @@
|
|
|
529
543
|
"types": "./types/ids-group-ltd-ids-design-system-components-icon-button.d.ts",
|
|
530
544
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs"
|
|
531
545
|
},
|
|
546
|
+
"./info-hint": {
|
|
547
|
+
"types": "./types/ids-group-ltd-ids-design-system-components-info-hint.d.ts",
|
|
548
|
+
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs"
|
|
549
|
+
},
|
|
532
550
|
"./input": {
|
|
533
551
|
"types": "./types/ids-group-ltd-ids-design-system-components-input.d.ts",
|
|
534
552
|
"default": "./fesm2022/ids-group-ltd-ids-design-system-components-input.mjs"
|
|
@@ -6,10 +6,6 @@ const scan_cjs_1 = require("./scan.cjs");
|
|
|
6
6
|
const STYLE_FILE = /\.(scss|css|sass|less)$/;
|
|
7
7
|
const TOKEN_ONLY_FILE = /\.(html|ts)$/;
|
|
8
8
|
const SKIPPED_DIR = /\/(node_modules|dist|\.angular)\//;
|
|
9
|
-
// `style.` catches `[style.--ds-x]="…"`, `setProperty('` catches
|
|
10
|
-
// `el.style.setProperty('--ds-x', …)`. Everything else on an .html/.ts line is prose or an
|
|
11
|
-
// unrelated binding, not a custom-property write.
|
|
12
|
-
const BINDING_MARKER = /style\.|setProperty\('/;
|
|
13
9
|
/**
|
|
14
10
|
* `ng g @ids-group-ltd/ids-design-system:check-overrides` — reports every `--ds-*` a consumer's
|
|
15
11
|
* stylesheets set that the installed version never reads, and every `ds-*` selector naming a class
|
|
@@ -29,13 +25,10 @@ function checkOverrides(options) {
|
|
|
29
25
|
if (!isStyleFile && !isTokenOnlyFile)
|
|
30
26
|
return;
|
|
31
27
|
const content = entry.content.toString('utf8');
|
|
32
|
-
const
|
|
33
|
-
? content
|
|
34
|
-
: content
|
|
35
|
-
|
|
36
|
-
.map((line) => (BINDING_MARKER.test(line) ? line : ''))
|
|
37
|
-
.join('\n');
|
|
38
|
-
for (const hit of (0, scan_cjs_1.findWriteOnlyTokens)(tokenSource, readTokens)) {
|
|
28
|
+
const tokenHitsInFile = isStyleFile
|
|
29
|
+
? (0, scan_cjs_1.findWriteOnlyTokens)(content, readTokens)
|
|
30
|
+
: (0, scan_cjs_1.findWriteOnlyBoundTokens)(content, readTokens);
|
|
31
|
+
for (const hit of tokenHitsInFile) {
|
|
39
32
|
context.logger.warn(`${path}:${hit.line} ${hit.token} is not read by @ids-group-ltd/ids-design-system ${surface.version}`);
|
|
40
33
|
tokenHits++;
|
|
41
34
|
}
|