Queries with same key should not share the same effect about query HOT 6 CLOSED

when Page mounts, it sets the query, which is in error state by then, back to loading state, after which the parent unmounts the Page and then it goes back into error state, mounting the Page, triggering another refetch.

This is the "expected" behaviour if you mount children like that without error handling, and the default retryOnMount: true setting.

from query.

Given that you agree to change current behavior, I'm happy to create a PR.

from query.

the refetch triggered in the Page should only affect the loading in the Page not in the parent.

I don't think that effect effectively propagated upwards forming a loop is "expected behavior"...

from query.

the refetch triggered in the Page should only affect the loading in the Page not in the parent.

if you use the same queryKey, there is only one cache entry, and that entry goes into loading state, and all components that are interested in that state will be informed about it.

from query.

loading should not be part of the shared cache. only data should be. loading is just a status from the initiator's perspective.

from query.

That might be what you want but it's not how it works because that's not how this lib was designed to work.

from query.