graphql-alt: Object version pagination

[amnn]

Description

Adding infrastructure for pagination, filters and filter intersection, and using it to implement pagination for object versions, exposed in the following fields:

• Query.objectVersions
• Object.objectVersionsBefore
• Object.objectVersionsAfter

Test plan

New unit tests for pagination logic:

sui$ cargo nextest run       \
  -p sui-indexer-alt-graphql \
  -- pagination

New E2E tests for new object pagination methods:

sui$ cargo nextest run         \
  -p sui-indexer-alt-e2e-tests \
  -- graphql/objects/object_versions

Stack

• graphql-alt: MovePackage #21950
• graphql-alt: consistency infra #21990
• graphql-alt: Query.package, Query.multiGetPackages #21991
• easy refactor(graphql-alt): lock down visibility #21992
• graphql-alt: Epoch #21997
• graphql-alt: ProtocolConfigs #22004
• graphql-alt: Epoch.coinDenyList #22005
• graphql-alt: latest Epochs and Protocol Configs #22006
• graphql-alt: indices for packages and epochs #22085

---

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.

• Protocol:
• Nodes (Validators and Full nodes):
• gRPC:
• JSON-RPC:
• GraphQL:
• CLI:
• Rust SDK:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sui-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 19, 2025 1:57pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
multisig-toolkit	⬜️ Ignored (Inspect)	Visit Preview		May 19, 2025 1:57pm
sui-kiosk	⬜️ Ignored (Inspect)	Visit Preview		May 19, 2025 1:57pm

[Copilot]

Pull Request Overview

This PR introduces pagination support for object versions in the GraphQL API, including new schema definitions, resolver functions, and pagination logic.

• Adds pagination fields (objectVersionsAfter, objectVersionsBefore) to the GraphQL schema and updates related API types.
• Implements and tests new pagination logic in the pagination module and integrates it into object and package queries.
• Adds helper functions for filter intersection to support version-bound queries.

Reviewed Changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
crates/sui-indexer-alt-schema/src/objects.rs	Updated Diesel model attributes for StoredObjVersion.
crates/sui-indexer-alt-graphql/staging.graphql, snapshots, schema.graphql	Added pagination fields and updated descriptions for object/package versions.
crates/sui-indexer-alt-graphql/src/pagination.rs	Added a new paginate_results method with tests for various paging scenarios.
crates/sui-indexer-alt-graphql/src/api/types/object.rs	Implemented new resolver functions for object_versions_after/object_versions_before and integrated filter intersection logic.
crates/sui-indexer-alt-graphql/src/intersect.rs	Introduced helper methods for merging filter boundaries.
crates/sui-indexer-alt-e2e-tests/tests/graphql/objects/object_versions.move	Added end-to-end tests for object versions pagination.

Comments suppressed due to low confidence (1)

crates/sui-indexer-alt-graphql/src/pagination.rs:271

• [nitpick] The logic for trimming prefix and suffix using nth and nth_back is complex; consider refactoring or adding explanatory comments to clarify how the edge trimming guarantees correct behavior.

if prefix > 0 { edges.nth(prefix - 1); }

[wlmyng]

i see, so this represents the result, where we have self.after(), then the first, last from fetched results, self.before()

[amnn]

Yep, this is lifted almost verbatim from OG GraphQL. The main difference is it doesn't include scan limit stuff.

[wlmyng]

whats the rationale for having two methods here, instead of a single objectVersions connection where you could paginate through all versions before or after the current package through the existing first, after, last, before params?

[amnn]

Just offering an objectVersions API is less expressive because there is no way to use that to phrase a "before" or "after" query, whereas the opposite is not true (you can phrase an objectVersions query as a combination of a before, after, and self query).