Skip to content

Commit

Permalink
Allow mutation execution to be purely syncronous
Browse files Browse the repository at this point in the history
  • Loading branch information
Azerothian committed Nov 12, 2018
1 parent 3023ef0 commit 7ef1389
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions spec/Section 6 -- Execution.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,17 +138,17 @@ ExecuteQuery(query, schema, variableValues, initialValue):

If the operation is a mutation, the result of the operation is the result of
executing the mutation’s top level selection set on the mutation root
object type. This selection set should be executed serially.
object type. This selection set and any sub selection set's should be executed serially.

It is expected that the top level fields in a mutation operation perform
It is expected that all fields in a mutation operation perform
side-effects on the underlying data system. Serial execution of the provided
mutations ensures against race conditions during these side-effects.

ExecuteMutation(mutation, schema, variableValues, initialValue):

* Let {mutationType} be the root Mutation type in {schema}.
* Assert: {mutationType} is an Object type.
* Let {selectionSet} be the top level Selection Set in {mutation}.
* Let {selectionSet} be the any Selection Set in {mutation}.
* Let {data} be the result of running
{ExecuteSelectionSet(selectionSet, mutationType, initialValue, variableValues)}
*serially*.
Expand Down

0 comments on commit 7ef1389

Please sign in to comment.