Allow preventing onSearchChange debounce by specifying null for loadThrottle #372
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brianreavis
added a commit
that referenced
this pull request
Apr 30, 2014
Allow preventing onSearchChange debounce by specifying null for loadThrottle
|
I think this a good idea too. Thanks man! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In unit testing our component that utilizes Selectize, I found that removing the debounce made things simpler to test since it removed the need to utilize timeouts and such to get everything to flow correctly. I'm not positive this is the best (or remotely ideal) way to handle this but it has been effective so far.