GraphQL Foundation Working Group Updates
This discussion topic proposes taking on the standardization of GraphQL over the WebSocket protocol. Together with that discussion, a new library for the WebSocket protocol has been created. Read the blog post to understand the reasoning behind this work and for links to the protocol RFC and the implementation library.
This is an RFC for a new "Tagged" type to be added to GraphQL to help address the input polymorphism feature gap. Originally proposed as the @oneField directive, the Tagged type has evolved into an entire new type in the type system, and is currently the lead proposal from the Input Unions Working Group. If you have use-cases for input polymorphism, please take a look. Feedback is very welcome.
This PR proposes the following 2 RFCs: formalizing the naming and definition of field coordinates and formalizing the way in which a Field Node (and list thereof) contained within a query document can be serialized as field coordinates. The RFC is filed, and the next action is to turn this into an actual spec edit.
Discussed whether the spec should allow deprecating an input that is required.
@lilianammmatos and @robrichard have made big progress on @deferer & @stream. A new experimental version of graphql-js was released with their changes and we want your help to try it out!
In the GraphQL ecosystem the term "query" can seem overloaded and ambiguous - sometimes it refers to the query operation type or a query operation, sometimes it refers to a GraphQL request or a GraphQL document containing operations, sometimes it refers to the contents of selection sets (as in "query reuse"), and sometimes it is used as a verb to refer to the generic act of querying a server for information. The WG discussed the best way to remove this ambiguity and how to move forward.
@andimarek and @eapache started the GraphQL Scalars initiative.