graphql-wg
graphql-wg copied to clipboard
graphql
Working group notes for GraphQL
@mjmahone [raised](https://github.com/graphql/graphql-wg/discussions/1051#discussioncomment-3327735) that the new increased cadence of WG meetings would impact on the TSC document. This edit attempts to maintain roughly the current level of commitment expected of TSC...
Presentation: https://docs.google.com/presentation/d/1qGc2rZKeim699tT-2G1xDESZP3Kd6tvj9V27tQfyJhg/edit#slide=id.ge9d8d484d6_0_5 > Lee: I agree with a lot of the ideas and problem statements from both presentations. To be respectful for time, we should have a discussion thread to...
### Context My team is looking to begin using the experimental `@defer` and `@stream` directives. The [spec](https://github.com/graphql/graphql-wg/blob/main/rfcs/DeferStream.md#defer) appears to leave prioritization up to the server. **I think this control structure...
The super early template is just to use as a starting point for this call: https://github.com/graphql/graphql-wg/discussions/1069#discussioncomment-3147894 Please feel free to send PRs to improve it.
> Rob: async feedback please on https://github.com/robrichard/defer-stream-wg/discussions/42 in robrichard/defer-stream-wg. Should we change name of “data” to “items” to make it clearer that it’s a different type. > Lee: thanks again...
We recently re-worked the spec with a focus on backwards compatibility and the introduction of a "watershed" for the `application/graphql+json` media type - after 1st Jan 2025 all GraphQL servers...
> ACTION: Lee: To collect the feedback, create a canonical discussion thread talking about the alpha release, things you want discussions on/etc - one nexus point for feedback. :new: Timestamped...