There was a undescribed "Breaking change" in useMutation hook

Since this commit there was a “breaking change” in the useMutation hook.

Intended outcome: When doing the following code:

const { errors } = await doMutation()

errors was filled if there was an error from the API

Actual outcome: Error is now thrown instead of returned.

How to reproduce the issue:

// Make sure this mutation returns a error
const { errors } = await doMutation()

// Errors wont be called since 
console.log(errors)

Versions Everything after 3.4.0

[jembach]

Hi @TriPSs,

I’m having the same problem. It is in my opinion an unexpected behavior because when i can get an error returned i expect that it does not throw an error. In addition it isn’t documented:

Currently my solution looks like this:

class ApolloCatchError implements ApolloQueryResult<undefined> {
  data = undefined;

  loading = false;

  networkStatus = NetworkStatus.error;

  errors = [];

  constructor(public error: ApolloError) {}
}

  async function fetchUser() {
    return gqlClient
      .query<QueryCurrentUserData, QueryCurrentUserVariables>({
        query: QUERY_CURRENT_USER,
        fetchPolicy: 'network-only',
      })
      .catch((error: ApolloError) => new ApolloCatchError(error));
  }

This is a typesafe solution providing the same result as @TriPSs and me expect

[TriPSs]

Yea, if the line where it now throws the error would return it just like it does a couple of lines above it the behaviour would be how it was.

Currently we have it this was in a lot of places, so if this behaviour won’t work anymore we would have to refractor all off those and add empty try catches to it otherwise our error reporting tool will send un needed messages.