-
Notifications
You must be signed in to change notification settings - Fork 540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix : DOM nesting Warning in BreadcrumbSeparator #9940
Conversation
WalkthroughThe pull request modifies the Changes
Assessment against linked issues
Possibly related issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for care-ohc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/components/ui/breadcrumb.tsx (1)
Line range hint
104-104
: Fix typo in BreadcrumbEllipsis display name.There's a typo in the display name: "BreadcrumbElipssis" has an extra 's'. While not related to the DOM nesting fix, we should correct it for consistency.
-BreadcrumbEllipsis.displayName = "BreadcrumbElipssis"; +BreadcrumbEllipsis.displayName = "BreadcrumbEllipsis";
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/components/ui/breadcrumb.tsx
(1 hunks)
🔇 Additional comments (1)
src/components/ui/breadcrumb.tsx (1)
82-90
: LGTM! The changes correctly address the DOM nesting warning.The switch from
<li>
to<span>
is the right approach here since the separator is decorative and shouldn't be part of the list structure. The accessibility attributes are maintained correctly.Let's verify that this component is used correctly throughout the codebase:
✅ Verification successful
Verified: The component changes are safe and all usages are compatible
The search results confirm that
BreadcrumbSeparator
is used consistently across the codebase, and no usage relies on theli
element behavior. All instances are simple separators within breadcrumb navigation, properly wrapped inBreadcrumbItem
components.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for any custom implementations or overrides of BreadcrumbSeparator # that might still expect an li element # Search for BreadcrumbSeparator usage rg -A 3 "BreadcrumbSeparator" --type tsx --type jsxLength of output: 79
Script:
#!/bin/bash # Search for BreadcrumbSeparator in ts, tsx, js, jsx files rg "BreadcrumbSeparator" -g "*.{ts,tsx,js,jsx}" -B 2 -A 3 # Also search for potential custom separator implementations rg "Separator.*=.*props" -g "*.{ts,tsx,js,jsx}" -B 2 -A 3Length of output: 4720
|
Can I work on this issue then ? |
Proposed Changes :
Screenshots :
Plz review : @ohcnetwork/care-fe-code-reviewers
Summary by CodeRabbit
<span>
instead of<li>