Skip to content

docs: clarify input element container incompatibility in React #622

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

iloveitaly
Copy link

What?

Wasted time debugging radar autocomplete with react :)

Why?

The docs did not make it clear that the <input/> reference is not compatible with React.

How?

doc change

Screenshots (optional)

NA

Anything Else? (optional)

I've written a ShadCN library for Radar. Can it be included in the documentation in some way?

https://github.com/iloveitaly/shadcn-radar-address-autocomplete

@Copilot Copilot AI review requested due to automatic review settings July 9, 2025 14:33
Copy link

vercel bot commented Jul 9, 2025

@iloveitaly is attempting to deploy a commit to the Radar Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the autocomplete documentation to clarify that using an <input/> element as the container ref is incompatible with React and may lead to unexpected DOM mutations.

  • Added a note explaining the incompatibility of <input/> as the container argument in React.
  • Instructed users to provide a non-input container reference when integrating with React.

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.

1 participant