Make auto-pagination use Relay's Cursor Connection Spec
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- graphql, typescript
- Domain
- api, backend-api-design
Research direction
The issue names no files, tests, or entry points. Start by locating graph-client's current auto-pagination behavior and comparing it with Relay's Cursor Connection Spec; done means adding compatible access to the specified connection structure without removing existing pagination methods.
Written by the indexing model from the issue text.
Description
The Cursor Connection Spec has become a de-facto standard in the larger GraphQL ecosystem, as far as I can tell. I first learned about it when using Gatsby, which uses the modified version of the Cursor Connection Spec advocated in this blog post: GraphQL Pagination best practices: Using Edges vs Nodes in Connections (this is my favorite post I've seen on the topic, as it is brief and contains links to other resources).
I have found graph-client's auto pagination difficult to work with on the client side, and would enjoy the flexibility and power offered by the Cursor Connection Spec. I also think this could be built in a backwards-compatible way, adding additional ways to access paginated data if people want to, without removing the method of pagination they're already using.
If y'all agree this is worth trying, I'll have time in my schedule in mid-September to try to help add it.
- Dominant language
- TypeScript
- Stars
- 186
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from graphprotocol/graph-client
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
graphprotocol/graph-client#1029 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphprotocol/graph-client#1031 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
graphprotocol/graph-client#1001 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
graphprotocol/graph-client#991 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
graphprotocol/graph-client#957 ·
All issues in graphprotocol/graph-client
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vercel-labs/just-bash#464 ·
-
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
TanStack/tanstack.com#1293 ·