Allow to trigger Suspense on every fetch request

[kamilkazmierczakMtab]

Currently Suspense is triggered only on initial fetch and it's not possible to display loader for next requests.

Imagine following situation:
User has list of items that display loader on initial fetch, then user goes into special page that displays details of selected item and makes changes there. After making mutation to this item he goes back to the list of items and react-query triggers fetch and unfortunately no loader is displayed and after some time (request ends) new values appear inside list which looks very weird from users perspective.

Currently there is no way to handle that scenario with react-query with Suspense, I could manually call setQueryData and update list cache with my values - but it's not always possible and also it should not be necessary.

Below is example with button that calls manually refetch and it would be great to somehow display loader from there
https://codesandbox.io/s/tender-worker-rve19u

[kamilkazmierczakMtab]

Following PR is not addressing this issue #3935

[kamilkazmierczakMtab]

It might be tricky because there are cases when in fact default behavior is desired.
Continuation of the example:
User can remove items on list so it would be nice to not show loader - in such case it's best to call setQueryData and invalidateQueries without triggering suspense.
So I think that the best solution to this would be to pass some argument to invalidateQueries to manually trigger Suspense with it - maybe some additional property to InvalidateOptions

[kamilkazmierczakMtab]

resetQueries solves this issue. We can close this discussion