-
Notifications
You must be signed in to change notification settings - Fork 434
Update to the June 2018 GraphQL spec #196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We should come up with a checklist of what we have to implement and have issues for everything. |
#219 switched from |
@LegNeato I think it would be useful to have a test suite based on https://github.com/graphql-cats/graphql-cats. That project seems to cover many scenario's, I think also beyond the June 2018 spec, but at least then we have an idea of what is supported and what is not. I'm not sure what the implementation would be exactly (a simple dynamic schema executor based on the scenarios'?) but the project is useful at least as a point of reference :) |
@LegNeato Ah nice, next time I'll make sure to do a search ;) Maybe I have this weekend time to have a look at it to see what we can do with it. |
Yes, this should be fixed. |
A new spec is out (https://github.com/facebook/graphql/releases/tag/June2018). It looks like a lot of our error handling questions / behaviors have been clarified among other things.
The text was updated successfully, but these errors were encountered: