Missing docs about aborted requests for V3

After upgrading to Apollo Client V3 - all the unmounted queries are aborted, which throws an error

• Message: The user aborted a request.
• Message: Fetch is aborted
• Message: The operation was aborted.

This is causing a lot of noise in the FE monitoring tools like raygun and etc (https://github.com/apollographql/apollo-client/issues/6769)

Looks like the docs are missing info about this change, I could not find it in either migration guide or in the docs search.

One of the users mentioned that passing the abort controller to the HTTP link helps, but has side effects. https://github.com/apollographql/apollo-client/issues/6769#issuecomment-962437610

With the abort controller passed - the requests are not aborted anymore, and no errors are thrown.

But is this the expected behavior? What is the right way to prevent abort errors to be thrown without breaking internal logic of the apollo client?

[jpvajda]

@bohdanbirdie 👋 I’ve added this issuer #6711 which is an umbrella issue for misc documentation updates that the team is currently iterating through. We accept PRs for our docs so if you wanted to make some improvements feel free to submit something and we can review. Thanks for being patient on this request!

[bohdanbirdie]

@bignimbus sorry, just noticed your message Out fix is quite specific and does not modify the apollo client in any way

For me it still looks like it would make sense to add docs about the AbortController, but I don’t exactly know what has changed in the Apollo v3 regarding that