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

no user input #27

Closed
rpedela opened this issue Jun 23, 2016 · 3 comments
Closed

no user input #27

rpedela opened this issue Jun 23, 2016 · 3 comments
Assignees
Milestone

Comments

@rpedela
Copy link

rpedela commented Jun 23, 2016

For my use case, I get all options from the server on the fly. When the textbox is focused and there is no user input yet, the options list is empty and it displays "no matches found". For my use case, that is very confusing to the user. In the case where there is no user input, how can I have it display nothing? I tried setting emptyLabel = null but it still renders an empty box of options. How can I make it render absolutely nothing for the options?

@ericgio
Copy link
Owner

ericgio commented Jun 23, 2016

Seems like a similar issue to the one described in #26.

Sounds like you want to just hide the dropdown by default until there is actually user input, which sounds reasonable.

@rpedela
Copy link
Author

rpedela commented Jun 23, 2016

Yes, exactly.

@ericgio ericgio modified the milestone: v0.5.2 Jun 24, 2016
@ericgio ericgio self-assigned this Jun 24, 2016
@ericgio ericgio added this to the v0.6.0 milestone Jul 18, 2016
@ericgio
Copy link
Owner

ericgio commented Jul 19, 2016

Added minLength prop in v0.6.0 so you can now specify how many characters the user must enter before the component will display the filtered results.

@ericgio ericgio closed this as completed Jul 19, 2016
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

No branches or pull requests

2 participants