coreui / coreui-pro / 32885885224

93%

main: 94%

push

github

docs(customize): name the theme tokens and colors the build emits (#886)

Four pages documented a theme surface that no longer matches the stylesheet,
so following them produced components that never respond to a theme class.

- `--cui-theme-base` does not exist; the generic slot is `--cui-theme-bg`.
  It was taught as public API in the token table, in the badge snippet, in
  the "define a brand of your own" CSS example, in the recipe for building a
  themeable component, and in the live button example on the buttons page —
  where the rendered button therefore stayed grey. Our own migration guide
  already records the rename.
- The badge snippet put the theme read inside the token map. The component
  reads the theme at the property, with its own token as the fallback; the
  snippet now shows both halves, because the map alone never picks up a theme.
- The theme color table still listed `light` and `dark`, which are not keys of
  `$theme-colors`, and omitted `inverse`, which is. It also gave `secondary` a
  fixed hex; `secondary` and `inverse` are `light-dark()` pairs.
- The badge has no `.badge-{color}` spelling, so the claim that every v5 color
  class keeps working was false for it.
- The color pages pointed at `scss/_config.scss` for `$colors`, `$grays` and
  `$theme-colors`, which live in `scss/_colors.scss` and `scss/_theme.scss`
  since the palette split, and printed `#9da5b1` for `$gray-500`, which is
  `#aab3c5`.

4532 of 5097 branches covered (88.92%)

Branch coverage included in aggregate %.

8653 of 9054 relevant lines covered (95.57%)

400.15 hits per line