2022-05-05.md

This is an open meeting: To attend or add agenda, send a Pull Request against this file.

GraphQL WG – May 2022

The GraphQL Working Group meets monthly to discuss proposed additions to the GraphQL Specification and other relevant topics to core GraphQL projects. This is an open meeting in which anyone in the GraphQL community may attend.

• Date & Time: May 5th 2022 18:00 - 20:00 UTC
  • View the calendar, or subscribe (Google Calendar, ical file).
  • Please Note: The date or time may change. Please check this agenda the week of the meeting to confirm. While we try to keep all calendars accurate, this agenda document is the source of truth.
• Video Conference Link: https://zoom.us/j/593263740
  • Password: graphqlwg
• Live Notes: Google Doc

Attendees

Name	GitHub	Organization	Location
Lee Byron	@leebyron	GraphQL Foundation	San Francisco, CA, US
Adron Hall	@adron	Amazon	Seattle, WA, US
Michael Staib	@michaelstaib	ChilliCream	Zurich, CH
Aubron Wood	@aubron	Google	Seattle, WA, US
Joey Nenni	@joeynenni	PayPal	Austin, TX, US
Yaacov Rydzinski	@yaacovcr	Individual	Neve Daniel, IL
Roman Ivantsov	@rivantsov	Microsoft	Seattle, WA
Rob Richard	@robrichard	1stDibs	New York, NY, US
Tim Suchanek	@timsuchanek	GraphCDN	Berlin, DE
Alex Reilly	@twof	Yelp	San Francisco, CA, US
Benjie Gillam ✏️	@benjie	Graphile	Chandler's Ford, UK
Hugh Willson	@hwillson	Apollo	Ottawa, ON, CA
Laurin Quast	@n1ru4l	The Guild	Oftersheim, DE
Matt Mahoney	@mmahoney	Meta	New York, NY
Saihajpreet Singh	@saihaj	The Guild	Ottawa, ON, CA
Morris Matsa	@mmatsa	IBM	Boston, US
Anthony Miller	@AnthonyMDev	Apollo	Las Vegas, NV
Arda Tanrikulu	@ardatan	The Guild	Istanbul, TR
Marc-Andre Giroux	@xuorig	Netflix	Montreal, Canada
Ivan Goncharov	@IvanGoncharov	Apollo	Lviv, UA
Doc Jones.	@doc-jones.	Postman	Raleigh, NC
Stephen Spalding	@fotoetienne	Netflix	Los Gatos, CA, US

Agenda

1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Lee)
   • Specification Membership Agreement
   • Participation Guidelines
   • Contribution Guide
   • Code of Conduct
2. Introduction of attendees (5m, Lee)
3. Determine volunteers for note taking (1m, Lee)
4. Review agenda (2m, Lee)
5. Review previous meeting's action items (5m, Lee)
   • Ready for review
   • All open action items (by last update)
   • All open action items (by meeting)
6. Discuss new intersection type proposal (15m, Yaacov)
   • Alternative to unions implementing interfaces discussed at last WG
   • spec PR: graphql/graphql-spec#941
   • graphql-js PR: graphql/graphql-js#3550
   • discussion: #944
7. Defer/Stream
   • asynchronous iterators of iterables versus of items, continuation of last WG meeting (15m, Yaacov)
     • Should resolvers returning AsyncIterables returning AsyncIterables of items or AsyncIterables of Iterables of items?
     • Should the AsyncGenerator returned by graphql-js yield items singly or yield all available items (in array or otherwise)?
     • Background: graphql/defer-stream-wg#38
     • See above link for polls, still waiting for feedback explaining votes.
   • Stream Payload index format (10m, Rob)
     • graphql/defer-stream-wg#39
8. CCN status update and rollout plans (10m, Alex Reilly)
9. @oneof - time to promote to RFC2? (20m, Benjie)
   • Spec PR
   • graphql.js PR (thanks @erikkessler1)
   • Main hesitation: should we mirror @oneof in the output types (i.e. type Foo @oneof { ... })
     • If yes: what does this mean for unions?
     • If yes: should we spec this a little before merging the input-only @oneof?
     • If no: is it desirable that input polymorphism and output polymorphism is so different?