-
Notifications
You must be signed in to change notification settings - Fork 11.6k
graphql-alt: IObject.objectAt, MovePackage.packageAt #22087
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds support for fetching objects and packages at alternative versions or checkpoints to enable updates on previously fetched data. Key changes include new GraphQL fields (objectAt and packageAt) in multiple schema files, corresponding resolver functions in the Rust API, and updated end-to-end tests validating the new behavior.
Reviewed Changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.
Show a summary per file
File | Description |
---|---|
crates/sui-indexer-alt-graphql/staging.graphql | Added new field definitions for objectAt and packageAt with descriptions |
crates/sui-indexer-alt-graphql/src/api/types/object.rs | Added resolver function for object_at |
crates/sui-indexer-alt-graphql/src/api/types/move_package.rs | Added resolver functions for object_at and package_at |
crates/sui-indexer-alt-graphql/schema.graphql | Added new field definitions for objectAt and packageAt in the core schema |
Tests | Updated snapshots and Move test scripts to validate the alternative version fetching |
Description
Support fetching a different version of an existing object or package. This is mostly helpful if you have fetched an object or package in response to some nested query, and then want to modify the version of it you are looking at.
Test plan
New E2E tests:
Stack
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.