Implemented MirrorNodeClientqueryTransaction #33
Closed
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
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.
#26
The TransactionInfo class was expanded to hold all the data that is indicated in the API call result as showed in the query sample of the issue with the corresponding data types.
Used the
@JsonCreatorand@JsonPropertyto map exact field names to JSON key names.The method
Optional<TransactionInfo> queryTransactionin the MirrorNodeClientImpl class has been updated to use an object mapper to covert the JSON data to aTransactionInfoobject finally return thetransactionInfoobject