coreui / coreui-pro / 33959166575

96%

main: 94%

push

github

feat(utilities)!: count the .rounded-* stops on the radius scale (#1172)

* feat(utilities)!: count the .rounded-* stops on the radius scale

The `.rounded-*` family still read the five v5 sizes
(`--cui-border-radius-sm` … `-xxl`), while every component had moved to the
`$radii` scale (`--cui-radius-0` … `-9`). Two radius systems, one of them
kept alive only for utilities.

`.rounded-{n}`, `.rounded-size-{n}` and the side classes now take their
values from `$radii`, so `.rounded-6` … `.rounded-9` exist and every number
means the same stop a component token reads. `.rounded` without a number is
stop 5, the radius buttons and controls use. A numbered `.rounded-{n}` also
writes `--cui-rounded-size`, so a side class next to it inherits the size;
the side classes set logical corners, so `.rounded-top` flips with the
writing direction like `.rounded-start` did.

`$border-radius`, `-sm`, `-lg`, `-xl`, `-xxl`, `-pill` and their tokens are
removed; nothing in `scss/` read them. `--cui-border-radius` stays on
`:root` as a deprecated alias of `--cui-radius-4`, because the shared docs
engine reads it for its own chrome and that engine serves v5 too. The
radius mixins default to `var(--cui-radius-5)` for the same reason: the
engine includes `border-radius()` without an argument.

BREAKING CHANGE: `.rounded-1` … `.rounded-5` change value (old → new stop:
1→3, 2→4, 3→5, 4→8, 5→9); the migration guide carries the table. The
`$border-radius*` variables and `--cui-border-radius-{sm,lg,xl,xxl,pill}`
tokens are gone.

* chore: raise the utilities CSS ceilings for the four new radius stops

.rounded-6 … .rounded-9 across six families put coreui-utilities.min.css at
19.53 kB against a 19.5 kB ceiling, and the unminified file had 0.13 kB left.
Ceilings move to 21 / 19.75 kB; size work is scheduled for the end of v6.

4837 of 5435 branches covered (89.0%)

Branch coverage included in aggregate %.

9268 of 9667 relevant lines covered (95.87%)

401.37 hits per line