docs: fix dead links, enable rule #2808
Conversation
|
|
WalkthroughRemoves ignoreDeadLinks from VitePress config, deletes a debug console.log in a Vue component, and updates numerous docs links/anchors. The grid-system docs receive additional link updates plus a new demo/code block. Migration guide links and wording are normalized. No API or behavioral changes. Changes
Sequence Diagram(s)Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
commit: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🔭 Outside diff range comments (1)
apps/docs/src/docs/components/table.md (1)
46-50: Normalize “Color Variants” links to the new types anchorThe page still points to
/docs/reference/color-variants, but elsewhere (e.g. line 958) we use/docs/types#colorvariant. Updating these links prevents inconsistencies now that dead-link checking is stricter.• File:
apps/docs/src/docs/components/table.md
Lines: 46–50-| `_cellVariants` | Partial<Record<keyof T, ColorVariant>> | Bootstrap contextual state applied to individual cells. Keyed by field (See the [Color Variants](/docs/reference/color-variants) for supported values). These variants map to classes `table-${variant}` or `bg-${variant}` (when the `dark` prop is set). | +| `_cellVariants` | Partial<Record<keyof T, ColorVariant>> | Bootstrap contextual state applied to individual cells. Keyed by field (See the [Color Variants](/docs/types#colorvariant) for supported values). These variants map to classes `table-${variant}` or `bg-${variant}` (when the `dark` prop is set). | -| `_rowVariant` | ColorVariant | Bootstrap contextual state applied to the entire row (See the [Color Variants](/docs/reference/color-variants) for supported values). These variants map to classes `table-${variant}` or `bg-${variant}` (when the `dark` prop is set) | +| `_rowVariant` | ColorVariant | Bootstrap contextual state applied to the entire row (See the [Color Variants](/docs/types#colorvariant) for supported values). These variants map to classes `table-${variant}` or `bg-${variant}` (when the `dark` prop is set) |
🧹 Nitpick comments (2)
apps/docs/src/docs/components/popover.md (1)
103-105: Minor wording polish for clarityTighten the sentence and avoid “directive version” phrasing.
-Refer to the [popover directive](/docs/directives/BPopover) docs on applying custom -classes to the directive version. +Refer to the [popover directive](/docs/directives/BPopover) docs for applying custom +classes when using the directive.apps/docs/src/docs/components/grid-system.md (1)
433-438: Fix a small typo: “o control” → “to control”Minor grammar fix.
-Use the `margin` and `padding` [spacing utilities](https://getbootstrap.com/docs/5.3/utilities/spacing) -o control how elements and components are spaced and sized. Bootstrap 5 includes a six-level scale for spacing +Use the `margin` and `padding` [spacing utilities](https://getbootstrap.com/docs/5.3/utilities/spacing) +to control how elements and components are spaced and sized. Bootstrap 5 includes a six-level scale for spacing
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (11)
apps/docs/.vitepress/config.mts(0 hunks)apps/docs/src/components/ComponentReference.vue(0 hunks)apps/docs/src/docs/components/_options.md(1 hunks)apps/docs/src/docs/components/avatar.md(1 hunks)apps/docs/src/docs/components/collapse.md(1 hunks)apps/docs/src/docs/components/form-input.md(1 hunks)apps/docs/src/docs/components/grid-system.md(7 hunks)apps/docs/src/docs/components/nav.md(1 hunks)apps/docs/src/docs/components/popover.md(2 hunks)apps/docs/src/docs/components/table.md(2 hunks)apps/docs/src/docs/migration-guide.md(7 hunks)
💤 Files with no reviewable changes (2)
- apps/docs/src/components/ComponentReference.vue
- apps/docs/.vitepress/config.mts
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: xvaara
PR: bootstrap-vue-next/bootstrap-vue-next#2701
File: apps/docs/src/docs/migration-guide.md:622-626
Timestamp: 2025-06-05T11:43:10.793Z
Learning: In migration guides, links to the old/previous version's documentation (like bootstrap-vue.org) are appropriate and helpful when explaining deprecated features, as they provide users with reference points for what they're migrating from.
📚 Learning: 2025-06-05T11:43:10.793Z
Learnt from: xvaara
PR: bootstrap-vue-next/bootstrap-vue-next#2701
File: apps/docs/src/docs/migration-guide.md:622-626
Timestamp: 2025-06-05T11:43:10.793Z
Learning: In migration guides, links to the old/previous version's documentation (like bootstrap-vue.org) are appropriate and helpful when explaining deprecated features, as they provide users with reference points for what they're migrating from.
Applied to files:
apps/docs/src/docs/components/_options.mdapps/docs/src/docs/components/popover.mdapps/docs/src/docs/migration-guide.md
📚 Learning: 2025-06-26T19:46:19.333Z
Learnt from: dwgray
PR: bootstrap-vue-next/bootstrap-vue-next#2762
File: apps/docs/src/docs/components/tooltip.md:0-0
Timestamp: 2025-06-26T19:46:19.333Z
Learning: BTooltip is a very thin wrapper around BPopover in bootstrap-vue-next. There is no separate `useTooltipController` composable - the `usePopoverController` composable can be used to programmatically control both popovers and tooltips.
Applied to files:
apps/docs/src/docs/components/popover.md
📚 Learning: 2025-04-28T22:48:46.738Z
Learnt from: xvaara
PR: bootstrap-vue-next/bootstrap-vue-next#2425
File: packages/bootstrap-vue-next/src/plugins/popoverController/index.ts:138-140
Timestamp: 2025-04-28T22:48:46.738Z
Learning: In bootstrap-vue-next, `PopoverOrchestratorParam` includes an `id` field of type `ControllerKey` through inheritance from base types. This field is declared in the `BvControllerOptions` interface and propagated through the type hierarchy.
Applied to files:
apps/docs/src/docs/components/popover.md
🪛 LanguageTool
apps/docs/src/docs/components/form-input.md
[grammar] ~192-~192: There might be a mistake here.
Context: ...per) for quickly creating a <datalist> from an array of options using the same ...
(QB_NEW_EN)
apps/docs/src/docs/components/avatar.md
[grammar] ~22-~22: There might be a mistake here.
Context: ...ons.getbootstrap.com/icons/person-fill/) when no other content is specified. You...
(QB_NEW_EN)
apps/docs/src/docs/components/popover.md
[grammar] ~103-~103: There might be a mistake here.
Context: ...ctives/BPopover) docs on applying custom classes to the directive version. For f...
(QB_NEW_EN)
apps/docs/src/docs/components/grid-system.md
[grammar] ~366-~366: There might be a mistake here.
Context: ...s/5.3/utilities/spacing) utility classes like .mr-auto to force sibling columns...
(QB_NEW_EN)
[grammar] ~428-~428: There might be a mistake here.
Context: ...etbootstrap.com/docs/5.3/utilities/flex) for sizing, alignment, spacing, and more...
(QB_NEW_EN)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: build
🔇 Additional comments (19)
apps/docs/src/docs/components/_options.md (1)
15-15: Confirmed ‘v-html’ Anchor Exists
- In apps/docs/src/docs/migration-guide.md (line 101), there is a
### v-htmlheading, so the/docs/migration-guide#v-htmllink target is valid.No further action needed—approving link normalization.
apps/docs/src/docs/components/collapse.md (1)
7-8: Directive link/docs/directives/BTogglevalidatedThe file
apps/docs/src/docs/directives/BToggle.mdexists with exact casing, so the links are correct.• Verified in
apps/docs/src/docs/components/collapse.mdat lines 7–8
• Verified inapps/docs/src/docs/components/collapse.mdat lines 16–17apps/docs/src/docs/components/avatar.md (1)
22-23: Good switch to canonical Bootstrap Icons URL for ‘person-fill’.Directly linking to icons.getbootstrap.com improves reliability and avoids internal redirects. Nothing further from my side.
apps/docs/src/docs/components/table.md (2)
498-503: Formatting-only change is fineThe inserted blank line after “specifying:” is harmless and improves readability.
958-959: Good: updated theming link to canonical types anchorSwitching to /docs/types#colorvariant aligns with the PR’s goal and removes a likely dead link under the stricter link check.
apps/docs/src/docs/components/popover.md (1)
6-6: LGTM: Directive link and filename casing verified
- Confirmed
apps/docs/src/docs/directives/BPopover.mdexists with exactBPopovercasing/docs/directives/BPopoverroute will resolve correctlyapps/docs/src/docs/components/grid-system.md (6)
56-56: LGTM: Bootstrap grid Sass link normalizedThe updated Bootstrap 5 link target looks correct.
221-221: LGTM: link to “Customizing the grid” is correctCanonical page/anchor confirmed.
354-355: LGTM: spacing utilities link modernizedUpdating to /docs/5.3/utilities/spacing is in line with the PR’s objectives.
416-419: LGTM: display utilities link is correctNo issues.
428-429: LGTM: flex utilities link is correctNo issues.
443-444: LGTM: visibility utilities link is correctNo issues.
apps/docs/src/docs/migration-guide.md (7)
238-242: LGTM: CombinedPlacement anchor normalizedLinking to /docs/types#combinedplacement is consistent with the new types anchor strategy.
433-434: LGTM: Direct link to component-specific docsPointing BFormCheckbox to its dedicated page improves discoverability.
462-462: LGTM: Direct link to component-specific docsPointing BFormRadio to its dedicated page improves discoverability.
495-498: LGTM: Direct link to component-specific docsPointing BFormSpinButton to its dedicated page improves discoverability.
653-653: LGTM: Alignment anchors unified to typesUsing /docs/types#alignment here is consistent with other pages.
663-663: LGTM: Navbar color-schemes linkPoints to the correct internal section.
667-667: LGTM: Alignment anchors unified to typesConsistent with the new internal anchor strategy.
| [`<BFormDatalist>`](/docs/components/form#datalist-helper) for quickly creating a `<datalist>` | ||
| from an array of options using the same options object as [`<BFormSelect>`](/docs/components/form-select#options-property). |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Datalist helper link anchor normalized — ensure target exists.
The move from /docs/components/form/#datalist-helper to /docs/components/form#datalist-helper is correct stylistically. Please verify the “datalist-helper” anchor is present on the Form docs page.
Check with:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Searching for 'datalist-helper' anchor in the Form docs..."
# Common file name guesses + fallback
for guess in apps/docs/src/docs/components/form.md apps/docs/src/docs/components/form/index.md; do
if [ -f "$guess" ]; then
echo "Checking $guess"
rg -n -C2 '^\s{0,3}#+\s+datalist[- ]helper\b' "$guess" || rg -n 'id="datalist-helper"' "$guess" || true
fi
done
# If unknown, scan all component docs
rg -n -C2 '^\s{0,3}#+\s+datalist[- ]helper\b' apps/docs/src/docs/components || rg -n 'id="datalist-helper"' apps/docs/src/docs/components || trueLength of output: 865
Missing “datalist-helper” anchor in Form docs – please add or correct link target
I searched apps/docs/src/docs/components/form.md (and its index) and didn’t find a heading or id="datalist-helper" anchor, so the link in form-input.md will 404.
• File & Lines: apps/docs/src/docs/components/form-input.md (192–193)
• Link: <BFormDatalist>
• Action: Add a ## Datalist helper {#datalist-helper} (or equivalent id="datalist-helper") entry to apps/docs/src/docs/components/form.md, or update the link to match an existing anchor.
🧰 Tools
🪛 LanguageTool
[grammar] ~192-~192: There might be a mistake here.
Context: ...per) for quickly creating a <datalist> from an array of options using the same ...
(QB_NEW_EN)
🤖 Prompt for AI Agents
In apps/docs/src/docs/components/form-input.md around lines 192 to 193, the link
to /docs/components/form#datalist-helper points to a non-existent anchor and
will 404; either add a heading with the id "datalist-helper" in
apps/docs/src/docs/components/form.md (e.g. add a "## Datalist helper
{#datalist-helper}" or equivalent HTML id on the appropriate section) or change
the link in form-input.md to the correct existing anchor in form.md so the
target resolves; update whichever file you modify and run the docs build/preview
to confirm the anchor link works.
| You can use [margin and spacing](https://getbootstrap.com/docs/5.3/utilities/spacing) utility classes | ||
| like `.mr-auto` to force sibling columns away from one another. | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Update Bootstrap 4 class example to Bootstrap 5 RTL-aware utilities
The example uses .mr-auto, which is Bootstrap 4 and LTR-only. In Bootstrap 5, use logical properties:
- .ms-auto to push an element to the end (margin-inline-start: auto)
- .me-auto to push following siblings (margin-inline-end: auto)
-You can use [margin and spacing](https://getbootstrap.com/docs/5.3/utilities/spacing) utility classes
-like `.mr-auto` to force sibling columns away from one another.
+You can use [spacing utilities](https://getbootstrap.com/docs/5.3/utilities/spacing), e.g. `.ms-auto`,
+to force sibling columns away from one another.If desired, double-check Bootstrap 5 docs for ms/me utilities:
🏁 Script executed:
#!/bin/bash
# Grep the repo for any remaining 'mr-auto' examples to update consistently
rg -n -C2 '\bmr-auto\b' apps/docs/src/docs || trueLength of output: 1264
Replace .mr-auto with Bootstrap 5 RTL-aware .me-auto in docs and demo
We’ve found remaining references to the old Bootstrap 4 utility in both the markdown and the Vue demo. Please update them to use the logical margin-inline-end: auto class (.me-auto).
• apps/docs/src/docs/components/grid-system.md (line 367)
-You can use [margin and spacing](https://getbootstrap.com/docs/5.3/utilities/spacing) utility classes
-like `.mr-auto` to force sibling columns away from one another.
+You can use [spacing utilities](https://getbootstrap.com/docs/5.3/utilities/spacing), e.g. `.me-auto`,
+to force sibling columns away from one another.• apps/docs/src/docs/components/demo/ColSpacing.vue (lines 37 & 42)
<BCol
cols="auto"
class="me-auto p-3 bg-info">cols="auto" .mr-auto</BCol>
--->
<BCol
cols="auto"
class="me-auto p-3 bg-info">cols="auto" .me-auto</BCol>This keeps the demo’s class attribute and its displayed snippet in sync with Bootstrap 5’s RTL-aware utilities.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| You can use [margin and spacing](https://getbootstrap.com/docs/5.3/utilities/spacing) utility classes | |
| like `.mr-auto` to force sibling columns away from one another. | |
| You can use [spacing utilities](https://getbootstrap.com/docs/5.3/utilities/spacing), e.g. `.me-auto`, | |
| to force sibling columns away from one another. |
🧰 Tools
🪛 LanguageTool
[grammar] ~366-~366: There might be a mistake here.
Context: ...s/5.3/utilities/spacing) utility classes like .mr-auto to force sibling columns...
(QB_NEW_EN)
🤖 Prompt for AI Agents
In apps/docs/src/docs/components/grid-system.md around lines 366-368 and in
apps/docs/src/docs/components/demo/ColSpacing.vue at lines 37 and 42, replace
the old Bootstrap 4 utility class `.mr-auto` with the Bootstrap 5 RTL-aware
logical class `.me-auto`; update both the rendered class attribute in the demo
component and any displayed code snippet in the markdown/demo so they match and
ensure there are no remaining `.mr-auto` references.
| [`AlignmentJustifyContent`](/docs/types#alignment): `start`, `center`, `end`, `between`, `around`, and `evenly`. | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Alignment types anchor updated — double-check the Types page exposes “alignment”.
Pointing to /docs/types#alignment aligns with other normalized anchors in this PR. Verify the “alignment” section (or equivalent) exists and slugifies to “alignment”.
Quick check:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Verifying 'alignment' anchor on types docs..."
# Try a common types doc location
for f in apps/docs/src/docs/types.md apps/docs/src/docs/types/index.md; do
if [ -f "$f" ]; then
echo "Checking $f"
rg -n -C2 '^\s{0,3}#+\s+alignment\b' "$f" || rg -n 'id="alignment"' "$f" || true
fi
done
# Fallback: search the entire docs for a types page with that heading
rg -n -C2 '^\s{0,3}#+\s+alignment\b' apps/docs/src/docs || trueLength of output: 635
Missing #alignment anchor in Types documentation
I updated the nav reference to /docs/types#alignment, but I couldn’t find any corresponding “alignment” heading or id="alignment" in apps/docs/src/docs/types.md. Please add or rename a section to:
## Alignment(or explicitly set id="alignment") so that the link resolves correctly.
🤖 Prompt for AI Agents
In apps/docs/src/docs/components/nav.md around lines 70 to 71, the nav links to
/docs/types#alignment but there is no corresponding "alignment" anchor in
apps/docs/src/docs/types.md; add a section header "## Alignment" (or an explicit
id attribute like <h2 id="alignment">Alignment</h2>) in that file near the
alignment/type descriptions so the fragment link resolves, and ensure the
section contains or references the Alignment/AlignmentJustifyContent details.
|
|
||
| [BootstrapVue](https://bootstrap-vue.github.io/bootstrap-vue/docs/components/modal#custom-rendering-with-slots) provides different slots to configure some pieces of the modal component. These slots are slightly different in [BootstrapVueNext](http://localhost:8000/bootstrap-vue-next/docs/components/modal.html#comp-reference-bmodal-slots): | ||
| [BootstrapVue](https://bootstrap-vue.github.io/bootstrap-vue/docs/components/modal#custom-rendering-with-slots) provides different slots to configure some pieces of the modal component. These slots are slightly different in [BootstrapVueNext](/docs/components/modal.html#comp-reference-bmodal-slots): | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Normalize modal slots link; avoid .html and questionable anchor
This link mixes a .html suffix and a nonstandard anchor. Elsewhere (Line 632) you link to /docs/components/modal#component-reference; consider aligning with that, or target a stable “Slots” section anchor if present.
-[BootstrapVue](https://bootstrap-vue.github.io/bootstrap-vue/docs/components/modal#custom-rendering-with-slots) provides different slots to configure some pieces of the modal component. These slots are slightly different in [BootstrapVueNext](/docs/components/modal.html#comp-reference-bmodal-slots):
+[BootstrapVue](https://bootstrap-vue.github.io/bootstrap-vue/docs/components/modal#custom-rendering-with-slots) provides different slots to configure some pieces of the modal component. These slots are slightly different in [BootstrapVueNext](/docs/components/modal#component-reference):Confirm the target anchor available in our modal docs:
🏁 Script executed:
#!/bin/bash
# Verify modal docs anchor names for slots/component reference
set -euo pipefail
rg -n -C2 '^(#|##)\s*(Component Reference|Slots)\b|slot' apps/docs/src/docs/components/modal.md || trueLength of output: 124
Let’s locate the actual modal docs file (it may be .mdx) and inspect its headings to confirm the correct anchor name:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Find any modal markdown/mdx files
echo "Modal doc files:"
find apps/docs/src/docs/components -type f \( -name 'modal.md' -o -name 'modal.mdx' \)
# For each, print the first 200 lines and show all headings
for f in $(find apps/docs/src/docs/components -type f \( -name 'modal.md' -o -name 'modal.mdx' \)); do
echo -e "\n--- $f ---"
sed -n '1,200p' "$f" | grep -nE '^#{1,6}\s'
doneLength of output: 729
Let’s search the entire modal.md for any “Component Reference” or “Slots” headings and any occurrences of “slot”:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="apps/docs/src/docs/components/modal.md"
echo "1) Headings for Component Reference or Slots:"
rg -nE '^#{1,6}\s*(Component Reference|Slots)\b' "$FILE" || echo "→ No matching headings found"
echo ""
echo "2) All occurrences of “slot” (case-insensitive):"
rg -ni 'slot' "$FILE" || echo "→ No “slot” occurrences found"Length of output: 640
Update BootstrapVueNext modal link
The current link in apps/docs/src/docs/migration-guide.md points to an anchor that doesn’t exist in your modal docs. Remove the .html suffix and the invalid #comp-reference-bmodal-slots anchor, linking instead to the base modal docs page:
- File:
apps/docs/src/docs/migration-guide.md, Line 639
Diff:
-[BootstrapVueNext](/docs/components/modal.html#comp-reference-bmodal-slots)
+[BootstrapVueNext](/docs/components/modal)🤖 Prompt for AI Agents
In apps/docs/src/docs/migration-guide.md around line 639, the modal docs link
includes a non-existent anchor and a .html suffix; update the href to point to
the base modal docs page by removing the ".html" suffix and deleting the
"#comp-reference-bmodal-slots" anchor so it links to the main modal docs URL
(e.g., the modal docs path without fragment or .html).
…keover * upstream/main: (21 commits) feat(b-form-rating): add `icon-clear` slot (#2809) docs: fix dead links, enable rule (#2808) chore: release main (#2801) docs: Fix navbar collapse behavior (#2802) docs: fix code tabs on getting started and icons pages (#2805) docs: fix missing data and use a stronger schema to catch missing errors (#2806) feat(BPopover): add explicit props for focus and hover triggers (#2795) fix(BNavbar): changed autoClose to noAutoClose and fix the documention mistake about it. fix: ssr in scrollspy docs: clean up css selector docs: fix on-this-page when examples use header tags docs(migration): add component aliases guidelines (#2771) chore: upgrade dependencies and address all lint warnings (#2785) chore: release main (#2769) fix(BDropdown): prevent hydration warning in nuxt production mode (#2768) docs(BTabs): Updates based on v-model changes (#2760) docs(table): fix missing anchor in `BTableLite` and `BTableSimple` links (#2759) docs(BFormRating): Parity pass (#2749) docs: fix typo in breadcrumb documentation (#2756) docs: Fix empty-text and empty-filtered-text description as they require show-empty to be set (#2755) ...
1 participant
Describe the PR
A clear and concise description of what the pull request does.
Small replication
A small replication or video walkthrough can help demonstrate the changes made. This is optional, but can help observe the intended changes. A mentioned issue that contains a replication also works.
PR checklist
What kind of change does this PR introduce? (check at least one)
fix(...)feat(...)fix(...)docs(...)The PR fulfills these requirements:
CHANGELOGis generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be deniedSummary by CodeRabbit