Do not forceUpdate if consuming component is not mounted

[wuarmin]

This change would fix the occurrence of the warning "Can't perform a React state update on an unmounted component" using useQuery in React.StrictMode.

#6209

best regards

[jgonera]

@wuarmin @brainkim Is anyone still working on this patch?

[wuarmin]

There are two failing tests. I have to invest some time, to find out, how they should be changed, or to check if their failing is correct. Can you help? Check out test details.

[wuarmin]

It would be great if someone with deeper knowledge of the project could check this 🙏

[brainkim]

I’m taking a look. The test suite is finicky. Thanks for the help!

[wuarmin]

I’m taking a look. The test suite is finicky. Thanks for the help!

@brainkim
Great, Thanks!

[brainkim]

Rebasing against release-3.4 seems to have fixed the breaking tests. I was doing work related to React.StrictMode which may have made the tests more robust maybe 🙈. It’s unfortunate that this might mean we might not get to backport it to 3.3 but 3.4 is looking to be a pretty nice release with a lot of fixes and stuff. Thanks for looking into this @wuarmin.

[wuarmin]

@brainkim thank you. I'm looking forward to 3.4.

[dylanwulf]

Thank you! I was experiencing this warning when a query unmounted at the same time as refetchQueries began. I'm not running in strict mode, but this change helped! 🎉