0.5.0-alpha: support Iroha post-2.0.0-rc.2.0 features
#262
+1,428
−747
Conversation
This file contains hidden or 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
Iroha changes: - Block query order - New model of transaction entrypoints/results
Contributor
Author
|
Superseded by #263 (it was a mistake to push into this repo directly, as it made |
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.
Upstream changes:
MerkleProof<T>struct (no first-class support in@iroha/core/cryptoyet)client.ws.blocks(), returning anAsyncGenerator<SignedBlock>(API is not finalized)client.find.blocks()andclient.find.blockHeaders()now require a payload like{ order: Order.Ascending }