graphql-wg
graphql-wg copied to clipboard
graphql
Working group notes for GraphQL
In the March WG last year, whilst trying to make the meetings easier to attend, we reduced their duration from 3 hours to 2 hours: https://github.com/graphql/graphql-wg/blob/389d6c4eef16a949fae6daa4f88973a85f36e20f/notes/2021-03-04.md#alternate-wg-meeting-times-15m-andi > Lee: maybe we...
> Benjie: As update, tried to rewrite graphql-js into spec text, as Lee took slightly different approach. > Action Item: look through spec text, make sure it matches graphql-js >...
> Potential validation oversight - @skip/@include; see related RFC: graphql/graphql-spec/pull/860 > ACTION - Benjie - raise a separate PR for this against GraphQL.js - assignee(s): @benjie - source: https://github.com/graphql/graphql-wg/blob/main/notes/2021-05-13.md#advancing-__typename-not-valid-at-subscription-root-rfc-15m-benjie ---...
> Lee: review the PR to see if it is doing everything we want it to; then we can find out if there's any resistance to promoting it to Approved....
> Benjie: We don’t have a rule in the spec that says arguments have to be unique. I’ve looked over the spec and it’s a very small change, which adds...
> Lee: I like this; this is very aligned with one of the principles of GraphQL - documentation as a first class concept. > Ivan: no-one opposed to moving it...
Context: relax rule on Field Selection Merging to allow merging covariant fields Spec PR (15m, Ivan) > Lee: I'd be dubious of completely removing it, whereas your proposed change here...
Strictly this was a "next steps" rather than an explicit "action". > Lee: Next steps: continue work on validation/execution. The PR that you have now is added but disabled; but...
[2021-06-03] Create a document in this repo so interested people can add themselves to @implementors
Context: the @graphql/implementers team > Ivan: suggest we create a do in the GraphQL WG repo so interested people can add themselves to it > Lee: good idea - good...
> Ivan: I mean like a String value - if I send surrogate pair inside as a literal; that'll be transcoded into proper code. What if I send it via...