You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I personally discovered this after bashing my head again the proverbial wall for 2 hours trying to work out why tags: true was doing absolutely nothing to my Select2 instance... only to discover that the project I'm working in sets minimumResultsForSearch: 5 in the global defaults.
so as a fix, might I suggest simply overriding or ignore the minimumResultsForSearch property for instances that use tags? it will only save one config setting in some cases, but it should help prevent a great many headaches.
The text was updated successfully, but these errors were encountered:
I would tend to agree with you that there are no situations where having tags enabled while having a minimum number of results for the search makes sense, so I've accepted this and marked it as a documentation fix. It would also make sense to raise a debug warning for any configuration where we detect these two being used together.
I have found that the "Dynamic Option Creation" feature breaks a little with a custom minimum result count applied to the "list search" feature.
I don't have a JSBin account, but I did verify this by setting these options in the template linked in the new issue text.
this can be reproduced with the following settings:
I personally discovered this after bashing my head again the proverbial wall for 2 hours trying to work out why
tags: true
was doing absolutely nothing to my Select2 instance... only to discover that the project I'm working in setsminimumResultsForSearch: 5
in the global defaults.so as a fix, might I suggest simply overriding or ignore the
minimumResultsForSearch
property for instances that usetags
? it will only save one config setting in some cases, but it should help prevent a great many headaches.The text was updated successfully, but these errors were encountered: