@apollo/client

Patch Changes

• Fix an issue where multiple fetches with results that returned errors would sometimes set the data property with an errorPolicy of none.

• Fix an issue where fetchMore would write its result data to the cache when using it with a no-cache fetch policy.

• Fix an issue where executing fetchMore with a no-cache fetch policy could sometimes result in multiple network requests.

Potentially disruptive change

When calling fetchMore with a query that has a no-cache fetch policy, fetchMore will now throw if an updateQuery function is not provided. This provides a mechanism to merge the results from the fetchMore call with the query's previous result.