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
Precedence of minimumResultsForSearch
vs. minimumInputLength
#6240
Comments
Yup, this is a feature request. Here's a quick explanation of why we can't universally do this.
I'm pretty sure the only time when we could allow them to be combined is when we can run a blank search to get the first page of results, which basically means only standard |
Ahh, I see the problem. Yes, in my case it would indeed be a local search on select options. Unfortunatelly I dont have the time to look into this. As a workaround I just disable the minLength requirement ^.^ |
This is a bug in my opinion but would qualify as a feature request.
Given the example below, with a dataset of 4 entries, I would expect that select2 will show the entire list instead of a message prompt to enter at least 1 character. After all, the search bar should be hidden before it checks for user input.
The text was updated successfully, but these errors were encountered: