-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
Minor documentation bug on AutoComplete component page #7296
Comments
I would rather say that it's an issue with the API of the AutoComplete. We can't do much without introducing a breaking change. |
I don't understand your comment. The docs specifically state that extra
props will be added to the root element. This is incorrect. The extra props
get added to the text field, according to the code.
…On Thu, Jun 29, 2017 at 11:38 PM Olivier Tassinari ***@***.***> wrote:
I would rather say that it's an issue with the API of the AutoComplete. We
can't do much without introducing a breaking change.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7296 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgUytEQ-kx0MfoNrukhJQwNjYp_QOgAks5sJJfrgaJpZM4OKLrD>
.
|
@jcheroske You are right. My point is that the comment should be enforce accros the component for simplicity. Making the code matchs the comment would introduce a breaking change. Given that the documentation is automatically generated. I would rather wait on the migration of the component to the v1-alpha branch. I hope that's more clear putted this way. |
Just to be clear, here's what I'm talking about:
The root is getting the root style, but not the props, even though the docs specifically say that the props go to the root. This is simply incorrect. |
Duplicate of #6292 |
Problem description
Documentation for AutoComplete props is incorrect. The following passage:
Should read:
The text was updated successfully, but these errors were encountered: