[GraphQL Client] Use checkpointSummaryBcs instead of manual conversion.
#62
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
stefan-mysten
commented
Nov 20, 2024
| @@ -448,6 +448,7 @@ type Checkpoint { | |||
| By default, the scanning range consists of all transactions in this checkpoint. | |||
| """ | |||
| transactionBlocks(first: Int, after: String, last: Int, before: String, filter: TransactionBlockFilter, scanLimit: Int): TransactionBlockConnection! | |||
| checkpointSummaryBcs: Base64 | |||
There was a problem hiding this comment.
Update the schema when PR in main repo gets merged.
stefan-mysten
force-pushed
the
gql_checkpoint_summary_test
branch
from
cebf70d to
31bc488
Compare
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.
Get checkpoint summary from bcs instead of manually converting it. This is dependent on first landing
MystenLabs/sui#20340
bcscomment.Note: this will have to sit for a while because we have no releases in the upcoming weeks so we cannot get an updated version of the CLI that includes the latest schema changes.