Skip to content
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.

Sign up for GitHub

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

Jump to bottom

June 2018 Spec compliance checklist #119

Open
1 of 6 tasks
anmonteiro opened this issue Sep 3, 2018 · 0 comments
Open
1 of 6 tasks

June 2018 Spec compliance checklist #119

anmonteiro opened this issue Sep 3, 2018 · 0 comments

Comments

@anmonteiro
Copy link
Contributor

anmonteiro commented Sep 3, 2018 •
edited
Loading

The following is an incomplete but growing list of things that we need to support to achieve compliance with the Jun 2018 version of the Spec.
anmonteiro added a commit to anmonteiro/ocaml-graphql-server that referenced this issue Dec 9, 2018
@anmonteiro
Add the errors key first in the response JSON
02868f1 
According to the `Response Format`
[section](https://facebook.github.io/graphql/June2018/#sec-Response-Format)
of the GraphQL Spec:

> When errors is present in the response, it may be helpful for it to
appear first when serialized to make it more clear when errors are
present in a response during debugging.

refs andreas#119
@anmonteiro anmonteiro mentioned this issue Dec 9, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anmonteiro