This is an open meeting: To attend, read JoiningAMeeting.md then edit and PR this file. (Edit: ✎ above, or press "e")

GraphQL WG – December 2023 (Primary)

The GraphQL Working Group meets regularly to discuss changes to the GraphQL Specification and other core GraphQL projects. This is an open meeting in which anyone in the GraphQL community may attend.

This is the primary monthly meeting, which typically meets on the first Thursday of the month. In the case we have additional agenda items or follow ups, we also hold additional secondary meetings later in the month.

• Date & Time: December 7, 2023, 10:30 AM – 12:00 PM PST
  • 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 Notes

Attendees

Name	GitHub	Organization	Location
Lee Byron (Host)	@leebyron	GraphQL Foundation	San Francisco, CA, US
Benjie Gillam	@benjie	Graphile	Chandler's Ford, UK
Matt Mahoney	@mjmahone	Meta	New York, NY, US
Jeff Auriemma	@bignimbus	Apollo	Monroe, CT, US
Alex Reilly	@twof	Independent	San Francisco, CA, US
Phil Prasek	@prasek	Apollo	Seattle, WA, US
Martijn Walraven	@martijnwalraven	Apollo	Amsterdam, NL
Michael Staib	@michaelstaib	ChilliCream	ChilliCream, CH
Yaacov Rydzinski	@yaacovCR	Individual	Neve Daniel, IL
Antoine Boyer	@tinnou	Netflix	San Jose, CA, US
Rafael Staib	@rstaib	ChilliCream	ChilliCream, CH
Jens Neuse	@jensneuse	WunderGraph	Frankfurt, GER
Anthony Miller	@AnthonyMDev	Apollo	Las Vegas, NV, US
Ivan Goncarov	@IvanGoncharov	Apollo	Lviv, UA
Rob Richard	@robrichard	1stDibs	Jersey City, NJ, US
Marc Giroux	@xuorig	Netflix	Montreal, Canada

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. Updates from the group formerly known as the Client Controlled Nullability WG (5m, Alex)
6. Review prior secondary meetings (5m, Lee)
   • November WG Secondary, APAC
   • November WG Secondary, EU
7. Subcommittee to work on standardizing distributed schemas (15m, Jeff)
   • There has been a lot of new excitement across the community around standardizing on an approach for working with distributed schemas, ranging from Open Federation to Fusion
   • We (Apollo) are excited about these developments, and are looking forward to working with others on this standardization approach
   • We haven't seen the afore mentioned standardization efforts be brought to the Working Group yet, so we'd like to get the ball rolling and start discussions
   • Should we start the composite schema subcommittee back up, to collaborate more closely? Or would folks like to explore an alternative approach?
   • Regardless, let's get the discussions going - super exciting!
8. Review previous meeting's action items (30m, Benjie)
   • #1345 - everyone review default value validation
     • Sufficient review time has elapsed; RFC is at stage 2 already - needs GraphQL.js merge for stage 3
   • #695 - no @skip/@include on subscriptions - raise GraphQL.js PR
     • GraphQL.js PR raised
     • Can we bump RFC to RFC2?
   • #1331 - if interface field deprecated, then object field should be deprecated
     • Spec PR and GraphQL.js PR raised
     • Advance to RFC1?
   • #1336 - coercing variable values in lists; clarify spec text
     • Discussed December 2022, but the issue was misinterpretted; it relates to variables inside lists, not in arguments directly
     • Spec editorial PR: fix bug in list coercion example table
     • Agenda item below: "Detail variables in list input coercion rules"
   • #1414 - example of executing selection set serially, readers expect an operation; clarify
     • Spec editorial PR: define "selection set" and clarify examples in section 6
   • #1337 - forbid nullable variable with default in non-nullable position
     • Agenda item below: "Introduce Strict and Legacy All Variable Usages Are Allowed validation rules"
   • #1413 - close all aging action items
     • Stale closed items
     • Note: not all items closed were "action items"
   • All open action items (by last update)
   • All open action items (by meeting)
9. Fix bug in CoerceArgumentValues() algorithm (10m, Benjie)
   • Spec PR
   • No GraphQL.js PR needed, GraphQL.js already implements the correct behavior
   • Spec bug: RFC process, or editorial?
10. Detail variables in list input coercion rules (15m, Benjie)
    • Spec PR
    • GraphQL.js already implements the correct behavior?
    • Previously discussed (but incorrectly interpreted) in December 2022: https://github.com/graphql/graphql-wg/blob/main/notes/2022/2022-12.md?rgh-link-date=2023-07-08T08%3A09%3A10Z#field-error-resulting-from-insufficient-validation-of-variables-15m-benjie
    • Not really changing behavior, just defining the status quo... Editorial, or RFC process?
11. Introduce Strict and Legacy All Variable Usages Are Allowed validation rules (15m, Benjie)
    • Spec PR
    • Aim: before I go about implementing this in GraphQL.js, are we agreed this is the right solution? RFC1?
    • Question: should we enable the new algorithm by default in the next major bump of GraphQL.js, and enable users to opt-in to the old version if they need to?