Draft
Conversation
|
🚨 End to end tests failed. Please check the failed workflow run. |
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 PR introduces new behavior in location search:
For filtering results, match any name that contains the search term string
Prefix matches rank higher than contains matches
“Starts with” ranks higher than second word
Words rank higher the sooner they occur in the name
Dashes are not spaces
Search terms are matched strictly, separate words are handled as a single string.
When searching for a child, do not display the parent as this makes searches like “Za” bring up Croatia, when in reality the user is probably looking for Zagreb.
This change is