Implement the GraphQL NodeState type properly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
The GraphQL NodeState model (raphtory-graphql/src/model/graph/node_state.rs) is currently a stopgap and needs a proper implementation covering the local NodeState/OutputNodeState surface: typed values, ordering, grouping (rows currently group by their debug representation via GroupKey), and paging.
Related existing issues (docs and naming only, no implementation ticket existed): #2334, #2272.
Raised in review: https://github.com/Pometry/Raphtory/pull/2675#discussion_r3811948480
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading raphtory-graphql/src/model/graph/node_state.rs and comparing its stopgap NodeState implementation with the local NodeState/OutputNodeState surface. Trace how typed values, ordering, grouping through GroupKey, and paging are represented, then confirm that the GraphQL model covers each area consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100