fix(core-api): fix wallet/transactions confirmations and timestamp fields #3761
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
…x/core-api/wallet-transactions
ghost
added
air1one
previously approved these changes
Jun 1, 2020
faustbrian
approved these changes
Jun 2, 2020
ghost
deleted the
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.
Summary
Includes #3733 (should be merged first), fixes #3758 and #3759, and comment in #3741. All related to search and api.
Similarly to #3733 new set of methods
...joinBlockare introduced toTransactionHistoryService. Joined block data is then used to calculateconfirmationsandtimestampin api response.Implemented
addresscriteria that searches by bothsenderIdandrecipientId. Note that it isaddress, notaddresseswhich similar to other fields (recipientId, notrecipientIds), but incompatible with v2.6.Checklist