Skip to content
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(listbox): listbox-section items prop in html #4369

Merged
merged 1 commit into from
Dec 22, 2024

Conversation

EReguero
Copy link
Contributor

@EReguero EReguero commented Dec 15, 2024

Closes #4277

📝 Description

Items props for ListBoxSection was shared to component in otherProps doing that items render in HTML. Same as before was fix for title i added to props list for prevent spread to component.

⛳️ Current behavior (updates)

Items and object are printed in HTML component
image

🚀 New behavior

Only correct props are printed
image

💣 Is this a breaking change (Yes/No):

No

📝 Additional Information

Summary by CodeRabbit

  • Bug Fixes

    • Resolved an issue with the rendering and management of items in the listbox component.
  • New Features

    • Improved functionality of the listbox by removing unnecessary properties to enhance user experience.

Copy link

changeset-bot bot commented Dec 15, 2024

🦋 Changeset detected

Latest commit: 208e1ee

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@nextui-org/listbox Patch
@nextui-org/autocomplete Patch
@nextui-org/select Patch
@nextui-org/react Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Dec 15, 2024

@EReguero is attempting to deploy a commit to the NextUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Dec 15, 2024

Walkthrough

The pull request addresses an issue with the @nextui-org/listbox package, specifically modifying the ListboxSection component. The changes involve removing the title and items properties from the component's props to prevent unwanted HTML element attributes. This modification aims to resolve rendering and functionality issues related to dynamic collections in the Listbox component.

Changes

File Change Summary
packages/components/listbox/src/listbox-section.tsx Removed title and items props from ListboxSectionProps interface
.changeset/angry-boxes-wonder.md Added changeset file to document the modification

Assessment against linked issues

Objective Addressed Explanation
Fix dynamic collections bug [#4277]
Resolve issues with items prop rendering

Possibly related PRs

Suggested reviewers

  • wingkwong
  • jrgarciadev

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. This feature will be included in our Pro Plan when released.


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?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

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.

@EReguero
Copy link
Contributor Author

I took same approach that was taken for title. If is there a common or cleaner way you use please tell me.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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)
.changeset/angry-boxes-wonder.md (1)

1-5: Consider enhancing the changeset message with more details.

While the message correctly identifies the fix, it would be helpful to include:

  • The specific issue that was fixed (items prop being rendered in HTML)
  • The impact of the fix
  • Any related changes (like the title prop handling)
-fix listbox section items prop in html element (#4277)
+fix(listbox): prevent items prop from rendering in HTML element of ListboxSection (#4277)
+
+Similar to the title prop fix, removes items prop from being spread to prevent
+unwanted HTML attributes in the rendered output.
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8d53e8b and 208e1ee.

📒 Files selected for processing (2)
  • .changeset/angry-boxes-wonder.md (1 hunks)
  • packages/components/listbox/src/listbox-section.tsx (1 hunks)
🔇 Additional comments (2)
packages/components/listbox/src/listbox-section.tsx (2)

54-56: Verify impact on component consumers.

While this change improves the HTML output, let's verify there are no consumers relying on these props being passed through.

✅ Verification successful

Let me gather more information about the component's implementation and its props handling.


Let me check the actual implementation and usage in the related files to understand how the items prop is handled.


Change is safe to proceed

The removal of the items prop from the HTML element is safe because:

  1. The component internally uses item.childNodes to render the list items, not the items prop directly
  2. All consumers in the codebase (tests, stories, and docs) use ListboxSection with children components rather than relying on the items prop being passed to the DOM
  3. The prop is properly handled before being excluded from the HTML attributes
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for ListboxSection usage patterns
rg -A 3 "ListboxSection.*items=" 

Length of output: 472


Script:

#!/bin/bash
# Check ListboxSection implementation and props handling
ast-grep --pattern 'interface ListboxSectionProps {
  $$$
}'

# Check for any other potential consumers
rg -l "ListboxSection"

Length of output: 813


Script:

#!/bin/bash
# Check the implementation in base component and stories
ast-grep --pattern 'const ListboxSection = $$$'

# Check usage in stories and docs
rg -A 3 "<ListboxSection" packages/components/listbox/stories/listbox.stories.tsx apps/docs/content/components/listbox/sections.raw.jsx

Length of output: 9593


54-56: Implementation looks good and follows established patterns.

The approach to exclude the items prop from HTML output is consistent with the existing title prop handling. The use of eslint-disable is appropriate here as we intentionally destructure these props to prevent them from spreading to the HTML element.

Let's verify that no other similar props need the same treatment:

✅ Verification successful

Props handling in ListboxSection is complete and correct

Based on the verification of both the component's props interface and implementation, the current handling of items and title props is sufficient. Looking at the props from ListboxSectionProps and ListboxSectionBaseProps, there are no other props that would need similar treatment to prevent them from being spread to the HTML element. All other props (variant, color, classNames, etc.) are meant to be passed through to affect the rendering.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for props that might be incorrectly rendered in HTML
ast-grep --pattern 'interface ListboxSectionProps {
  $$$
}'

Length of output: 62


Script:

#!/bin/bash
# Let's try a different approach to find the ListboxSection component and its props
rg -A 10 "interface ListboxSectionProps" packages/components/listbox/src/

Length of output: 949


Script:

#!/bin/bash
# Also search for any spread props in the component implementation
ast-grep --pattern 'const ListboxSection = ({ $$$, ...otherProps }: ListboxSectionProps)'

Length of output: 91


Script:

#!/bin/bash
# Look for any other props being used in the component
rg -A 20 "const ListboxSection" packages/components/listbox/src/

Length of output: 2266


Script:

#!/bin/bash
# Let's check the base props interface to see all available props
rg -A 10 "interface ListboxSectionBaseProps" packages/components/listbox/src/

Length of output: 1124


Script:

#!/bin/bash
# Search for any other spread operations in the component's JSX
ast-grep --pattern '<$_
  $$$
  {...otherProps}
  $$$
/>'

Length of output: 2079

@EReguero EReguero changed the title fix(listbox): listbox-section props in html fix(listbox): listbox-section items prop in html Dec 15, 2024
@wingkwong wingkwong added this to the v2.6.9 milestone Dec 16, 2024
Copy link

vercel bot commented Dec 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nextui-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 18, 2024 0:44am
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 18, 2024 0:44am

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.

[BUG] - <Listbox dynamicCollections />
3 participants