Option: matchAnyQueryToken (default false) #2
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.
Bloodhound's tokenizer functions are a really powerful way to tune the search. Unfortunately this flexibility ends at
SearchIndex.prototype.search
. Currently datums must match ALL query-tokens (with no option to match ANY query-token). This pull request adds the option:Inspired by Elasticsearch's
MUST
andSHOULD
, matching ANY query-token opens up the possibility for more fuzzy search strategies. For more details see the tests and the following example:Note: Ideally this option could change from search-to-search. But I didn't want to clutter the
Bloodhound#search
api.