This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 457
Allow fuzzy search on data filter when getting transactions - Closes #2404 #2513
Merged
MaciejBaj
merged 11 commits into
development
from
2404-allow_fuzzy_search_on_data_filter
Nov 8, 2018
Merged
Allow fuzzy search on data filter when getting transactions - Closes #2404 #2513
MaciejBaj
merged 11 commits into
development
from
2404-allow_fuzzy_search_on_data_filter
Nov 8, 2018
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
vitaly-t
reviewed
Oct 31, 2018
vitaly-t
previously approved these changes
Oct 31, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
MaciejBaj
previously approved these changes
Nov 2, 2018
4miners
previously approved these changes
Nov 6, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks fine. However, I'm not sure about the feature itself. What is the point of allowing wildcard search on this field? I don't really see use cases for it.
4miners
reviewed
Nov 6, 2018
f6f5652
to
90e2f81
Compare
4miners
reviewed
Nov 6, 2018
4miners
previously approved these changes
Nov 7, 2018
nazarhussain
previously approved these changes
Nov 8, 2018
Co-Authored-By: diego-G <diego@lightcurve.io>
MaciejBaj
approved these changes
Nov 8, 2018
nazarhussain
approved these changes
Nov 8, 2018
4miners
approved these changes
Nov 8, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What was the problem?
Query was returning only exact matches.
How did I fix it?
Changing the subquery to support
LIKE
matches and removing null characters from the string to avoid errors.How to test it?
mocha test/functional/http/get/transactions.js
Review checklist