Skip to content

Commit e048e83

Browse files
committed
Change order of fields inside Response
To reflect change from graphql/graphql-js#838
1 parent 951971b commit e048e83

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

spec/Section 7 -- Response.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -85,16 +85,16 @@ objects in the response as unordered Maps and arrive at a valid value.
8585

8686
A response to a GraphQL operation must be a map.
8787

88-
If the operation included execution, the response map must contain a first entry
89-
with key `data`. The value of this entry is described in the "Data" section. If
90-
the operation failed before execution, due to a syntax error, missing
91-
information, or validation error, this entry must not be present.
92-
93-
If the operation encountered any errors, the response map must contain a next
88+
If the operation encountered any errors, the response map must contain a first
9489
entry with key `errors`. The value of this entry is described in the "Errors"
9590
section. If the operation completed without encountering any errors, this entry
9691
must not be present.
9792

93+
If the operation included execution, the response map must contain a next entry
94+
with key `data`. The value of this entry is described in the "Data" section. If
95+
the operation failed before execution, due to a syntax error, missing
96+
information, or validation error, this entry must not be present.
97+
9898
The response map may also contain an entry with key `extensions`. This entry,
9999
if set, must have a map as its value. This entry is reserved for implementors
100100
to extend the protocol however they see fit, and hence there are no additional

0 commit comments

Comments
 (0)