fix(autocomplete): popover should remain open after clicking clear button

[abhinav700]

Closes #3783

📝 Description

Added state.open() so that dropdown does not close when clear button is clicked.
based on this PR

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

Summary by CodeRabbit

Summary by CodeRabbit

• New Features
  • Enhanced the autocomplete component to keep the dropdown open when the clear button is pressed, allowing for a smoother user interaction experience.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6127840

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

This PR includes changesets to release 2 packages

Name	Type
@nextui-org/autocomplete	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

[vercel]

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

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the @nextui-org/autocomplete package, specifically altering the behavior of the clear button within the autocomplete component. The changes ensure that the dropdown remains open when the clear button is pressed, allowing users to continue interacting with the dropdown seamlessly. The state.open() method is now invoked on the clear button's onPress event, while the state.close() method has been removed.

Changes

Files	Change Summary
.changeset/dirty-moles-refuse.md	Introduces updates to the clear button behavior in the autocomplete component, ensuring the dropdown remains open after clearing the input.
autocomplete.test.tsx	Adds two test cases to verify that the autocomplete listbox remains open after clicking the clear button, for both standard and controlled components.

Assessment against linked issues

Objective	Addressed	Explanation
Autocomplete does not work when the clear button is hit (regression) (#3783)	✅

Possibly related PRs

• fix: popover-based focus behaviour #2854: Modifies the behavior of the clear button in the autocomplete component.
• fix(autocomplete): ignore pointer events when the clear button is hidden #3000: Addresses focus management of the clear button in the autocomplete component.
• fix(autocomplete): remove unnecessary state.close #3464: Removes unnecessary state.close() call in the autocomplete component.
• fix(autocomplete): highlight item in AutocompleteSection during keyboard navigation #3726: Enhances keyboard navigation in the AutocompleteSection.

Suggested reviewers

• jrgarciadev

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 046a9df and 6127840.

📒 Files selected for processing (1)

• .changeset/dirty-moles-refuse.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .changeset/dirty-moles-refuse.md

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.

[ryo-manba]

Thanks for the PR! The behavior looks good.
Could you add some tests?

[abhinav700]

@ryo-manba Sure, I will try to add some test cases

[abhinav700]

@ryo-manba I have added the test cases.

In the new test cases, I have not checked if the value is being cleared or not because that functionality is already covered in the previous test cases.

[abhinav700]

@ryo-manba I have made the changes.

[ryo-manba]

Nice! Thanks for your contribution!