Some GraphQL servers return an empty error array, even though it's not spec compliant PART II

[elhorowitz]

This issue is related to #156

Intended outcome:
Mutations should not return rejected promises if the server response includes an empty errors array.

While this behavior is technically spec compliant:

The errors entry in the response is a non‐empty list of errors, where each error is a map... If no errors were encountered during the requested operation, the errors entry should not be present in the result.

Some servers (like graphql-java) do not follow the specs explicitly: graphql-java/graphql-java#473

Actual outcome:
Successful mutation responses using the graphql_java server provide the following on success:

{
  data: { Response },
  errors: [],
  extensions: []
}

The apollo-client mutation code (specifically this line) rejects the query if response.errors exists, so it is therefore rejecting successful requests.

#173 updated apollo client's query code to be less rigid, a similar fix is needed for mutations.

Version

• [email protected]

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions to Apollo Client!

[stale]

This issue has been automatically closed because it has not had recent activity after being marked as stale. If you belive this issue is still a problem or should be reopened, please reopen it! Thank you for your contributions to Apollo Client!