Benjie
I think specifying auth tokens via query params is very risky; but that’s by-the-bye - I have no issue with someone implementing control of headers (I’m surprised we don’t already...
@github-actions publish-pr-on-npm
I want to add an introspection field indicating the default error behavior of a schema, so I've moved this to draft.
Exactly that, yes. `schema @behavior(onError: NO_PROPAGATE) { query: Query }` or some such. We _can_ do them separate, but I'd like to make it so that the presence of the...
This is now up to date with the latest version of the spec RFC, including the removal of `onError` on responses and the addition of `__Schema.defaultErrorBehavior` to introspection and `@behavior(onError:...
@github-actions publish-pr-on-npm
Thanks so much for contributing some documentation! Just a heads up that this is an unusually busy time for me: I just came back from vacation yesterday and on Saturday...
Another option: ```graphql enum __ErrorBehavior { """ Non-nullable positions that error cause the error to propagate to the nearest nullable ancestor position. The error is added to the "errors" list....
So I thought about this more, and as Yaacov says, `INLINE` is actually orthogonal to error behavior - it can be used with any of the modes. So actually maybe...
It's more legible when reading the response data as a human/developer. Rather than seeing `null` and then checking in a separate list to see if that's a "legit null" or...