default errorPolicy : "all" about apollo-client HOT 3 CLOSED

thank you @jerelmiller that helped

from apollo-client.

Hey @schoenbergeringo 👋

Just an FYI, our community forums or Discord server are a great place for these types of questions 🙂.

Unfortunately I haven't been around long enough to know the original motivation behind the decision to make none the default 🙁. I can at least say that the most common way users treat errors in queries is to ignore any partial results and instead just show some type of error indication. This being the most common form of error handling, the "none" default fits this well. Again, I have no idea if this is the reason its the default or not and unfortunately its a breaking change to switch to anything else at this point.

Is there a central place to set this errorPolicy to what i want ?

Yes! You can set defaultOptions in the constructor that will be used as the default for all queries/mutations in your app. Assuming you're using the query hooks (useQuery, useLazyQuery, etc), you'll want to set the error policy on the watchQuery options:

new ApolloClient({
  defaultOptions: {
    watchQuery: { 
      errorPolicy: 'all'
    }
  }
});

Using defaultOptions still allows you to override the errorPolicy per-query if you need something more specific:

useQuery(query, {
  // will be used instead of the default 'all'
  errorPolicy: 'none'
});

from apollo-client.

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better.

from apollo-client.