Skip to content

docs(MultiSelect): put the version badge under the heading, not after the prose - #700

Merged
mrholek merged 1 commit into
v6-devfrom
docs/added-in-placement-v6
Aug 4, 2026
Merged

docs(MultiSelect): put the version badge under the heading, not after the prose#700
mrholek merged 1 commit into
v6-devfrom
docs/added-in-placement-v6

Conversation

@mrholek

@mrholek mrholek commented Aug 4, 2026

Copy link
Copy Markdown
Member

Spotted by mrholek. The chips section had <AddedIn version="6.0.0" /> trailing its description:

  ### Chips

- Add `data-coreui-selection-type="chips"` to render selected options as … a labelled remove button. <AddedIn version="6.0.0" />
+ <AddedIn version="6.0.0" />
+
+ Add `data-coreui-selection-type="chips"` to render selected options as … a labelled remove button.

Every other section on the page — Global search two headings above, for instance — states the version first and then describes the feature. Trailing it means a reader finds out it is new only after reading what it does.

Rendered order confirmed on the built page: heading → "Added in v6.0.0" → prose.

Swept the rest of the docs for the same shape. Two other hits:

  • offcanvas had the badge on its own line but with a stray leading space — normalised.
  • alerts keeps its inline badge: there it marks a single bullet in a list as new, not a whole section, which is a different thing and reads correctly as it is.

… the prose

Every other section states the version before describing the feature; the
chips section had the badge trailing the paragraph, so a reader learned it
was new only after reading what it does.

Also drops a stray leading space before the offcanvas badge. The one in the
alerts list stays inline — there it marks a single bullet as new rather
than the whole section, which is a different thing.
@mrholek
mrholek merged commit 67d49d3 into v6-dev Aug 4, 2026
9 checks passed
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 30960939096

Coverage remained the same at 92.975%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 8674
Covered Lines: 8279
Line Coverage: 95.45%
Relevant Branches: 4821
Covered Branches: 4268
Branch Coverage: 88.53%
Branches in Coverage %: Yes
Coverage Strength: 362.79 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants