Skip to content

Conversation

xvaara
Copy link
Contributor

@xvaara xvaara commented Jun 14, 2025

Describe the PR

fixes #2693

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)

  • Bugfix 🐛 - fix(...)
  • Feature - feat(...)
  • ARIA accessibility - fix(...)
  • Documentation update - docs(...)
  • Other (please describe)

The PR fulfills these requirements:

  • Pull request title and all commits follow the Conventional Commits convention or has an override in this pull request body This is very important, as the CHANGELOG is 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 denied

Summary by CodeRabbit

  • Style
    • Updated the default CSS classes applied to active navigation links for improved consistency across components. The BLink component now uses a simplified default class for exact active links, while the BNavItem component now includes a predefined class for exact active links.

Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

coderabbitai bot commented Jun 14, 2025

Walkthrough

The changes modify the default values of the exactActiveClass prop in two Vue components: BLink and BNavItem. In BLink, the default class is reduced to 'router-link-exact-active'. In BNavItem, the default is set to 'router-link-exact-active active' from previously being undefined.

Changes

File(s) Change Summary
.../BLink/BLink.vue Changed exactActiveClass prop default from 'router-link-exact-active active' to 'router-link-exact-active'.
.../BNav/BNavItem.vue Changed exactActiveClass prop default from undefined to 'router-link-exact-active active'.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BNavItem
    participant BLink

    User->>BNavItem: Render component without exactActiveClass prop
    BNavItem->>BNavItem: Use default 'router-link-exact-active active'

    User->>BLink: Render component without exactActiveClass prop
    BLink->>BLink: Use default 'router-link-exact-active'
Loading

Assessment against linked issues

Objective Addressed Explanation
Ensure nav elements get correct active classes when using router (#2693)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Poem

The links now glow with classes new,
As navs and routers guide you through.
Exact or active, styles align,
Navigation’s looking fine!
With every hop and every click,
The bunny’s code is now more slick. 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 018daa5 and bdab363.

📒 Files selected for processing (2)
  • packages/bootstrap-vue-next/src/components/BLink/BLink.vue (1 hunks)
  • packages/bootstrap-vue-next/src/components/BNav/BNavItem.vue (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: test-unit
  • GitHub Check: test-lint
  • GitHub Check: build
🔇 Additional comments (2)
packages/bootstrap-vue-next/src/components/BLink/BLink.vue (1)

41-41: ⚠️ Possible breaking change – active class dropped for exact-active links outside BNavItem

Changing the default from 'router-link-exact-active active' to 'router-link-exact-active' means that a plain <BLink> now no longer receives the bootstrap "active" class when the route is exact-active.
Inside <BNavItem> that class is re-added (see the companion change), but any standalone <BLink> previously relying on the implicit "active" styling will silently lose it.

Please double-check:

  1. Storybook / docs examples that showcase <BLink> are still visually correct.
  2. Other components that forward exactActiveClass to <BLink> (e.g. BListGroupItem, custom in-app usages) don’t depend on the old default.

If the change is intentional, consider a note in the CHANGELOG + migration guide.
Otherwise, keep the previous default and let callers override when needed.

packages/bootstrap-vue-next/src/components/BNav/BNavItem.vue (1)

36-36: 👍 Active class now applied at the navigation-item level

Setting the default to 'router-link-exact-active active' aligns <BNavItem> with Bootstrap’s expectation that the "active" class sits on the link when it’s the exact route match. This also removes the need for custom templates to add "active" manually.

No issues spotted with the change itself.


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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

pkg-pr-new bot commented Jun 14, 2025

bsvn-vite-ts

npm i https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next@2747
npm i https://pkg.pr.new/bootstrap-vue-next/bootstrap-vue-next/@bootstrap-vue-next/nuxt@2747

commit: bdab363

@VividLemon
Copy link
Member

I don't know the best thing to do here. But perhaps it could be best to double check other components as well?

@xvaara xvaara merged commit 1e9b644 into bootstrap-vue-next:main Jun 16, 2025
5 checks passed
@github-actions github-actions bot mentioned this pull request Jun 16, 2025
xvaara added a commit to xvaara/bootstrap-vue-next that referenced this pull request Jul 29, 2025
* upstream/main:
  docs: clean up css selector
  docs: fix on-this-page when examples use header tags
  docs(migration): add component aliases guidelines (bootstrap-vue-next#2771)
  chore: upgrade dependencies and address all lint warnings (bootstrap-vue-next#2785)
  chore: release main (bootstrap-vue-next#2769)
  fix(BDropdown): prevent hydration warning in nuxt production mode (bootstrap-vue-next#2768)
  docs(BTabs): Updates based on v-model changes (bootstrap-vue-next#2760)
  docs(table): fix missing anchor in `BTableLite` and `BTableSimple` links (bootstrap-vue-next#2759)
  docs(BFormRating): Parity pass (bootstrap-vue-next#2749)
  docs: fix typo in breadcrumb documentation (bootstrap-vue-next#2756)
  docs: Fix empty-text and empty-filtered-text description as they require show-empty to be set (bootstrap-vue-next#2755)
  fix InputGroupXPend.vue
  chore: release main (bootstrap-vue-next#2748)
  feat: implement BFormRating component (bootstrap-vue-next#2744)
  chore: release main
  fix(BLink): move active class to BNavItem (bootstrap-vue-next#2747)
  feat(BDropdown): allow setting icon prop on nested BButton (bootstrap-vue-next#2746)
  fix(BToast): close BToast correctly if modelValue is changed from number to false (bootstrap-vue-next#2745)
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.

Nav active classes and maybe other aren't working when using router
2 participants