rmosolgo / rmosolgo/graphql-ruby
Update @defer to match the latest RFC
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.4k
- Forks
- 1.4k
- Avg merge
- 23h 19m
- Merged PRs (30d)
- 28
Description
GraphQL-Pro's @defer and @stream implementations predate the current RFC, but since then, the proposal has been updated and the latest Apollo client has better support for it. GraphQL-Pro should be compatible with the latest spec, but also, I need some way to keep compatibility for old users.
RFC: https://github.com/graphql/graphql-wg/blob/main/rfcs/DeferStream.md
It looks to me like the only difference is whether or not it's allowed on fields -- besides that, GraphQL::Pro::Defer and GraphQL::Pro::Stream look up-to-date to me.
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 with the linked DeferStream RFC and inspect the GraphQL::Pro::Defer and GraphQL::Pro::Stream entry points mentioned in the issue. Confirm how field usage differs in the latest spec, then define a compatibility path for old users; done means current Apollo clients and existing users are both supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, ruby
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100