@uni-design-system/uni-core 8.3.1 → 9.0.0

package/CHANGELOG.md

@@ -1,5 +1,231 @@
 # @uni-design-system/uni-core
 
+## 9.0.0
+
+### Major Changes
+
+- [`8250162`](https://github.com/uni-design-system/uni/commit/8250162c35e418f976080904df4c20783feeb6e2) Thanks [@gaenglish](https://github.com/gaenglish)! - Every deprecated API is removed. The library now carries no `@deprecated`
+  symbols at all.
+
+  **Per-component duration options → the `motion` scale.** Six components carried
+  their own duration knob that predated the motion scale and _won over_ it:
+  `expand.transitionSpeed`, `callout.transitionMs`, `radio.transitionSpeed`,
+  `menuItem.transitionSpeed`, `alert.transitionSpeed` and
+  `snackbar.transitionDelay`. All are gone, along with the precedence branch each
+  one required — timing now comes from the token, full stop.
+
+  Retime the token instead; one edit covers every component pointing at it. To
+  retime a single component, define a token of your own and point that
+  component's `motion` option at it:
+
+  ```ts
+  createTheme({
+    …,
+    motion: { productive: { duration: 110, easing: 'ease' } },
+    components: { menuItem: { options: { motion: 'productive' } } },
+  });
+  ```
+
+  A `duration: 0` token is how a theme opts out of motion — that is what
+  `transitionSpeed: 0` used to mean. Both showcase themes are migrated this way
+  (Carbon to a 110ms `productive` token, Wellsourced to an `instant` one).
+
+  **Options that never did anything.** `card.transitionSpeed` and
+  `inputBox.transitionSpeed` were read by nothing and never had been. Delete them
+  from your theme; nothing replaces them.
+
+  **Renames and obsolete APIs**
+  - `inputBox.typeFace` → `typeface` (the casing every other component uses).
+  - `uni-tooltip`'s `appendToBody` input — inert since the tooltip moved to the
+    native top layer, which escapes any overflow context by itself.
+  - Box's `elevation` input → `shadow`, in both the Angular and React packages.
+    It was a second name for the same thing.
+  - The Angular `icons` re-export → import `BaseIcons` from
+    `@uni-design-system/uni-core`. The default set ships with every theme.
+
+  **The HSL color legacy is gone from uni-core.** `uniColor`, `randomRangeValue`,
+  `CategorySaturation` and `CategoryLightness` are removed, superseded by the
+  deterministic OKLCH engine (`generateThemes` / `generatePalette`) — same input,
+  same theme, WCAG-checked. `RoleHues` and the `UniColor` type go with them: they
+  were reachable only through `uniColor`, and `RoleHues` had gone stale enough to
+  hold saturation values in a table of hues.
+
+  **Deferred output renames.** Three outputs were held back because renaming is
+  breaking; this is that release. Each also drops an eslint escape it needed for
+  shadowing a native event name or using an `on` prefix.
+
+  | Component            | Before            | After            |
+  | -------------------- | ----------------- | ---------------- |
+  | `uni-debounce-input` | `(change)`        | `(valueChange)`  |
+  | `uni-search-input`   | `(change)`        | `(searchChange)` |
+  | `uni-search-input`   | `(search)`        | `(searchSubmit)` |
+  | `dragAndDrop`        | `(onFileDropped)` | `(fileDropped)`  |
+
+  **`uni-dropdown`'s `color` input → `containerColor`,** completing the rule the
+  layout directives set: every container-pair input in the library is now
+  `containerColor`, and plain `color` always means the CSS property.
+
+  **`ThemeService.getSpacing('none')` now returns `0`, not the string `'none'`.**
+  `'none'` is not a valid length, so it was silently dropped wherever it landed —
+  `uni-menu` carried a comment working around exactly that, which is now deleted.
+
+- [`c0c6056`](https://github.com/uni-design-system/uni/commit/c0c6056c61e994a45af9c379f3c99f55eebcb79a) Thanks [@gaenglish](https://github.com/gaenglish)! - The spacing scale is open, and `createTheme` finally accepts one.
+
+  The scale was a closed seven-name union on a doubling curve (2/4/8/16/32/64px).
+  Real layouts are rarely built exclusively on one — the gaps between 8 and 16,
+  and 16 and 32, are where a lot of real spacing lives — and there was no way to
+  add a step, because **`ThemeConfig` had no `spacing` field at all**:
+  `createTheme` hardcoded the base scale. The Wellsourced showcase theme had to
+  bolt its scale on after the fact with a post-hoc spread.
+
+  Three changes, which only work together:
+  - `NullableSize` gains a `(string & {})` arm, so any name the theme defines is a
+    valid `padding` / `gap` / `marginInline` value while the seven named steps keep
+    their autocomplete. `Size` itself stays closed — it also types _component_
+    sizes, where an arbitrary name has nothing to resolve against.
+  - `Spacing` is spelled out as named-optional-keys plus an index signature
+    (mirroring `Typography`), rather than a `Partial<Record<…>>` that would
+    collapse to a plain string record and lose the named steps.
+  - `createTheme({ spacing })` merges over the base scale.
+
+  ```ts
+  createTheme({ id, name, colors, spacing: { tight: '6px', snug: '10px' } });
+  ```
+
+  ```html
+  <div stack-layout padding="tight" gap="snug">…</div>
+  ```
+
+  Because the scale is open, a mistyped token can no longer be a compile error. It
+  is dropped — an `undefined` CSS value simply does not render — and
+  `ThemeService` now warns once per unknown token in development, naming the
+  tokens the active theme does define. Scaffolded `uni-theme.ts` files carry a
+  `spacing` block so the static theme file stays the editable source of truth.
+
+  **Behavior change:** `xxl` was in the `Size` union but defined by no base theme,
+  so `padding="xxl"` type-checked and rendered nothing. It is now `128px`,
+  completing the doubling — any element relying on the silent drop will start
+  showing spacing.
+
+## 8.4.0
+
+### Minor Changes
+
+- [`1aca747`](https://github.com/uni-design-system/uni/commit/1aca747c7bdff6cf72a9fa349e77a6e7985b97c7) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-callout` and `uni-expand` now read their timing from the theme's `motion`
+  scale, so every animated surface in the library is retimed from one place.
+  They were the last two carrying their own motion options — in different units,
+  under different names (`transitionMs` in milliseconds, `transitionSpeed` in
+  seconds).
+
+  A third token joins `popup` and `panel`:
+
+  | Token    | Default           | Used by               |
+  | -------- | ----------------- | --------------------- |
+  | `reveal` | 350ms ease-in-out | expand, expand-toggle |
+
+  `reveal` is a _base_ speed, not a final duration: `uni-expand` still scales it
+  by content height (√-of-height, clamped) so short regions stay snappy and tall
+  ones aren't rushed, and its easing now drives the reveal curve, which was
+  hardcoded. `uni-expand-toggle` resolves the token the same way, so the chevron
+  and the region cannot drift apart. `uni-callout` maps onto `panel`, whose
+  250ms matches what it already used.
+
+  **Not breaking.** `transitionMs` and `transitionSpeed` are deprecated but
+  still honoured, and deliberately outrank `motion` — a theme that set either
+  keeps precisely its current timing rather than being retimed underneath it.
+  They are removed next major. Per-instance inputs, like `uni-expand`'s
+  `transitionSpeed`, still outrank everything.
+
+  Nothing moves differently by default: callout renders 0.25s ease and expand
+  0.35s ease-in-out exactly as before, verified against the rendered styles.
+
+- [`6f76c1d`](https://github.com/uni-design-system/uni/commit/6f76c1d3cc1ba2ed5e2747b6d2142d16cb4f537b) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-alert`, `uni-snackbar`, `uni-radio` and `uni-menu-item` now read their
+  timing from the theme's `motion` scale, which completes the migration: every
+  animated component in the library is retimed from one place.
+
+  Two tokens join `popup`, `panel` and `reveal`:
+
+  | Token          | Default           | Used by          |
+  | -------------- | ----------------- | ---------------- |
+  | `notification` | 350ms ease-in-out | alert, snackbar  |
+  | `control`      | 300ms ease        | radio, menu-item |
+
+  **One thing moves differently:** `menu-item`'s hover transition goes from
+  0.35s to 0.3s, joining `radio` on the shared `control` token. The two were
+  never deliberately different — `radio`'s own option documented its 0.3 as
+  "matching menuItem", which was not true — so this corrects drift rather than
+  changing a decision. A theme that wants the old timing can set the deprecated
+  `transitionSpeed`, or retime `control`. Everything else is byte-identical,
+  verified against the rendered styles.
+
+  **Deprecated, still honoured, removed next major:**
+  `alert.transitionSpeed`, `snackbar.transitionDelay`, `radio.transitionSpeed`
+  and `menuItem.transitionSpeed` all still work and still outrank `motion`, so a
+  theme that set them keeps its exact timing. `menu-item`'s escape hatch is
+  intact too: with neither the option nor a token set it still renders no
+  transition at all, and a token with `duration: 0` is the way to ask for
+  instant now.
+
+  `card.transitionSpeed` and `input-box.transitionSpeed` are also deprecated,
+  for a different reason: **neither was ever read by its component.** Setting
+  them has never had any effect. They are removed next major and nothing needs
+  to replace them.
+
+  `uni-skeleton` is deliberately left out. Its shimmer is a loop rather than a
+  transition, and folding a repeating animation into a scale built around
+  entering and leaving would make the scale mean two different things.
+
+- [`228c17f`](https://github.com/uni-design-system/uni/commit/228c17f9fb7a4e4eb8d6a9cd0a6301d02ddd3dd3) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-skeleton` picks up the knobs an app theme could not reach. `color`, `highlightColor` and `borderRadius` are now inputs that take a token name and fall back to the theme option, because one screen routinely needs several of each — text bars and a pill chip do not share a corner (`borderRadius="max"`), and a skeleton on a card wants a different tint than one on the page background.
+
+  The shimmer is now a band swept with `transform` rather than an animated `background-position`: it composites instead of repainting every frame, and its geometry is themeable via two new options, `direction` (`'ltr' | 'rtl'`, default `'ltr'` — the sweep previously ran right-to-left) and `highlightWidth` (band width as a percentage of the block, default `40`). Both ends of the band are the base color, so it dissolves into the block with no alpha and no fringing.
+
+  A new `label` input announces a standalone skeleton: set it and the host becomes `role="status"` with visually hidden text instead of `aria-hidden="true"`. Unlabelled skeletons stay `aria-hidden`, so container-level `aria-busy` patterns are unchanged.
+
+- [`3b51ace`](https://github.com/uni-design-system/uni/commit/3b51acee92659526c1c8c91668b37db8c5933162) Thanks [@gaenglish](https://github.com/gaenglish)! - Overlay timing is now a theme token. `UniTheme` gains a `motion` scale
+  alongside `radii`, `shadows` and the rest, and the overlays point at it by
+  name instead of carrying their own hardcoded durations.
+
+  Until now a theme could slow a skeleton shimmer but not a dropdown: `expand`,
+  `skeleton` and `callout` each exposed their own motion option while
+  `uni-dropdown` hardcoded 100ms and the combobox-style listbox popups copied
+  that constant. Retiming the library meant editing components.
+
+  Two tokens ship, because two things genuinely move differently — a small panel
+  attached to a control snaps, a larger free-floating surface settles:
+
+  | Token   | Default            | Used by                                                                     |
+  | ------- | ------------------ | --------------------------------------------------------------------------- |
+  | `popup` | 100ms linear, ×0.8 | dropdown, menu, multi-select, combobox, search-input, tag-input, time-input |
+  | `panel` | 250ms ease         | popover                                                                     |
+
+  A token carries `duration` (ms), `easing`, and an optional `scale` for panels
+  that grow into place — one token rather than separate duration and easing
+  scales, because they are one design decision: slowing a panel without
+  softening its curve reads as sluggish rather than calm.
+
+  ```ts
+  createTheme({
+    id: 'Calm',
+    name: 'Calm',
+    colors,
+    motion: { popup: { duration: 240, easing: 'ease-out', scale: 0.95 } },
+  });
+  ```
+
+  Tokens you don't restate keep their base values, and a component can still
+  point at a token of its own through its `motion` option.
+
+  Nothing moves differently by default — every current duration, easing and
+  scale is preserved exactly, verified against the rendered styles. Themes that
+  predate the scale keep working: `createTheme` fills it in, the validator does
+  not require it, and a theme registered as JSON without it resolves to the base
+  timing rather than failing. `motionSafe` remains the floor, so a theme decides
+  how overlays move for people who want movement, never whether they move at
+  all.
+
+  `callout`'s existing `transitionMs` option and the `expand`/`skeleton`
+  durations are untouched for now; folding them into this scale is a follow-up.
+
 ## 8.3.1
 
 ## 8.3.0