coreui / coreui-pro / 33960296034

94%

main: 94%

push

github

fix(theme): merge $theme-colors through defaults() and test the @use with() surface (#1174)

`$theme-colors` and `$theme-state-colors` were plain `!default` maps, so
`@use "coreui" with ($theme-colors: ("custom": (…)))` replaced the whole
map: the custom colour compiled and `--cui-primary-base` and every other
built-in vanished. Both maps now go through `defaults()` like the rest of
the configuration, so an entry adds, a full sub-map replaces one colour
and `null` removes one. Compiled CSS is unchanged.

The docs taught `map.merge($theme-colors, …)` after `@use "theme"` and
before `@use "coreui"`, which never took effect: `@use` rules are hoisted,
so the library had already loaded when the merge ran. The theme, sass and
color-modes pages now configure the map through `with ()`, use the `border`
slot the map actually reads (not `border-subtle`) and the `-base` token in
the focus ring; the migration snippet follows.

Five sass-true suites cover this surface: alert tokens through `with ()`,
a custom spacer and badge variant merged on top of the built-ins, root
token overrides and additions, a custom theme colour that keeps `primary`,
and the validation selector gating `:user-*` behind `[data-coreui-validate]`.

4837 of 5435 branches covered (89.0%)

Branch coverage included in aggregate %.

9268 of 9667 relevant lines covered (95.87%)

401.34 hits per line