Fuzzy Matching #60
Merged
Fuzzy Matching #60
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
ISSUE 45 - Fuzzy Matching
|
Can you do these things?
|
Updating startup.pgsql to include initializing the fuzzy matching extension, pg_trgm (Line 2)
jedmund
approved these changes
May 23, 2020
Merged
jedmund
added a commit
that referenced
this pull request
May 23, 2020
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.
Updates to Fuzzy Matching using postgresql pg_trgm extension, allowing us to use nonspecific search terms for gacha characters/summons. This is in response to Issue 45
Ex. 'jeanne' matches 'Jeanne d'Arc (Dark)', 'Jeanne d'Arc (Grand)' etc.
Spark:
Gacha:
Updated gacha.js and spark.js, as well as their helper function helpers/decision.js to handle the new operator, and updated datasets.