Updated search settings to be more accurate/extend search range of sh… #543
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Description
Before, searching for words like "groceries" would not work properly (e.g. Scotty's Market wouldn't show up). This was due to the fact that the default location distance was 60, so the search for "groceries" would only be performed on the first 60 characters of the Scotty's Market description. This pull request fixes this issue.
Additionally, the previous threshold of 0.3 meant that "Italian" spots on campus would appear in search results looking for "Asian" because of the similarity of "__alian" and "asian." To avoid this, I lowered the fuzzy search threshold to 0.1