Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
## Description Factor out a helper for calculating the relevant range of indices based on cursors/page information. This was previously part of `paginate_indices`, but will be used in the implementation of `MoveValue.asVector` as well, so it makes sense to have it as a separate function. ## Test plan New unit tests: ``` $ cargo nextest run -p sui-indexer-alt-graphql ```
## Description Add the ability to paginate over a vector of Move Values in the GraphQL API. This addresses a gap that made it more difficult to work with `vector`, `VecMap, and `VecSet` in GraphQL, compared to working with dynamic field based types like `Table` and `Bag`. ## Test plan New E2E tests: ``` $ cargo nextest run -p sui-indexer-alt-e2e-tests \ --test transactional_tests \ -- graphql/move_value/as_vector ```
## Description Give users the ability to refer directly to the value being displayed, using `$self`. This makes it possiblet to write expressions where the `$self` is used as part of a dynamic field key, rather than part of the parent that that dynamic field is being fetched from. E.g. to use the value as a key to fetch from a registry, `@REGISTRY->[$self]`. ## Test plan New unit tests: ``` $ cargo nextest run -p sui-display ```
jessiemongeon1
pushed a commit
to jessiemongeon1/sui
that referenced
this pull request
Mar 5, 2026
## Description Give users the ability to refer directly to the value being displayed, using `$self`. This makes it possiblet to write expressions where the `$self` is used as part of a dynamic field key, rather than part of the parent that that dynamic field is being fetched from. E.g. to use the value as a key to fetch from a registry, `@REGISTRY->[$self]`. ## Test plan New unit tests: ``` $ cargo nextest run -p sui-display ``` ## Stack - MystenLabs#25479 --- ## 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: - [ ] Indexing Framework:
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Give users the ability to refer directly to the value being displayed, using
$self. This makes it possiblet to write expressions where the$selfis used as part of a dynamic field key, rather than part of the parent that that dynamic field is being fetched from. E.g. to use the value as a key to fetch from a registry,@REGISTRY->[$self].Test plan
New unit 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.