feat(match_phrase): Use match_phrase lib#111
Merged
orangejulius merged 1 commit intomasterfrom Oct 3, 2019
Merged
Conversation
This uses the match_phrase helper function defined in #109 to cut down on duplication when creating `match_phrase` queries. Since the structure of the `match_phrase` query is defined in one place, it makes the resulting view code a bit more concise. It will also make optional parameter handling easier and more consistent.
orangejulius
added a commit
that referenced
this pull request
Oct 3, 2019
This change builds on the previous series of PRs (#112, and #111) to support the `slop` parameter on the `match_phrase` queries responsible for handling street addresses. Replaces #101 Connects pelias/api#1322
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This uses the match_phrase helper function defined in #109 to cut down on duplication when creating
match_phrasequeries.Since the structure of the
match_phrasequery is defined in one place, it makes the resulting view code a bit more concise.It will also make optional parameter handling easier and more consistent.