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.

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

Make 'errors' top property in the response object. #838

Merged
merged 1 commit into from
May 12, 2017

Conversation

IvanGoncharov
Copy link
Member

It’s hard to notice errors property if it is hidden under multiple screens of JSON.
For example, if you run this query you will see the following:
image
And only if you scroll a couple pages down you will see an error what is bad DX.
To fix this I just changed the order of errors and data fields so result of the same query look like this:
image

@leebyron leebyron merged commit 7287c7c into graphql:master May 12, 2017
@leebyron
Copy link
Contributor

I'm into it. Good idea

IvanGoncharov added a commit to IvanGoncharov/graphql that referenced this pull request Nov 21, 2017
leebyron pushed a commit to graphql/graphql-spec that referenced this pull request Nov 29, 2017
* Change order of fields inside Response

To reflect change from graphql/graphql-js#838

* Update Section 7 -- Response.md

Remove "first" and "next" and include an explicit note about errors appearing first when serialized as a convenience.
@IvanGoncharov IvanGoncharov deleted the fieldsOrder branch December 14, 2017 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants