• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

coreui / coreui-pro / 32762876575
94%
main: 94%

Build:
Build:
LAST BUILD BRANCH: feat/blocks-widgets-v6
DEFAULT BRANCH: main
Ran 24 Aug 2026 06:32PM UTC
Jobs 1
Files 67
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

24 Aug 2026 06:31PM UTC coverage: 93.174%. Remained the same
32762876575

push

github

web-flow
docs(utilities): give every property its own page (#872)

* docs(utilities): give every property its own page

The utilities section grouped several properties per page — `text` carried nine,
`spacing` four, `borders` four, `sizing` two, `interactions` two. That shape cost
us in two places. A reader looking for `gap` landed on a page about margin and
padding and had to scroll, and the docs MCP server resolves a slug by directory,
so properties without a page of their own were unreachable by name.

23 pages become 45. The five fully-split pages are gone and redirect to the
property that carried their name; `flex` and `grid` keep their own subject and
hand alignment off to the new pages.

The `$utilities` map is unchanged — only its `scss-docs` markers are split, so
each page quotes the entries it documents rather than the whole family it used to
share. Verified by compiling before and after: the emitted CSS is byte-identical.
Two pages quote two blocks each, because their entries are not adjacent in the
map, and reordering the map to make them adjacent would change the order utility
classes are emitted in.

Two fixes fell out of the split. `borders` had a `## Border-width` heading over
content about border colour, with the real widths further down under `## Width`;
those are now the border and border-color pages, each about what its title says.
And `.text-reset` sat on the text page though it sets `color` — it moved to
`colors`, next to the other colour utilities.

* docs(utilities): close example blocks at the indent they open

The array-form examples put the opening tag at column 0, the children at 4 and
the closing tag at 2. The engine hides that while a page passes only `html` — it
derives and normalises the shown source itself — so it has never been visible
here. It becomes visible the moment a page passes `code`, which the framework
editions must in order to show JSX, and it shipped that way in the React port
until review caught it.

Seventeen ex... (continued)

4532 of 5097 branches covered (88.92%)

Branch coverage included in aggregate %.

8653 of 9054 relevant lines covered (95.57%)

400.12 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32762876575.1 24 Aug 2026 06:32PM UTC 67
93.17
GitHub Action Run
Source Files on build 32762876575
  • Tree
  • List 67
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #32762876575
  • 9643b946 on github
  • Prev Build on v6-dev (#32734472436)
  • Next Build on v6-dev (#32762916653)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc