Automatically decode XDR values in getTransaction
#129
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.
The RPC response schemas for retrieving transaction details have been upgraded to parse the base64-encoded XDR automatically. Succinctly,
GetTransactionResponse
->RawGetTransactionResponse
GetTransactionResponse
includes the full, decoded XDR structures instead of raw, base64-encoded strings for the relevant fieldsHere is the full list of changed fields:
Notice that we also provide a property that is a parsed
returnValue
out of the meta, if possible. The true, raw, underlying schema is still accessible by adding theRaw
prefix to the interface name.