feat(core-api): search transactions by asset #2618
Merged
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.
Summary
The
/transactions/search
endpoint now accepts anasset
object.Internally it uses the
@>
(contains) operator for comparing the payload against thejsonb
column.For example this payload:
returns all transactions with an asset.
Whereas this one:
only returns type 2 transactions.
And lastly this
returns one matching transaction.
Note: Due to how
@>
works it is not possible to e.g. search for all assets with a username starting with "b" or with a number greater or equal something. Another limiting factor is our used sql query builder which makes it difficult to impossible to express more sophisticated statements.What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR release a new version?
Checklist