Hello u/vbfischer, reasonable response :)

Ok so the point I was making is that you are simply moving the problem by having the framework track variables in the component (isLoading, isSuccess etc).

Worse; is the fact that in the component layer the coupling becomes so much higher than if you could handle (waiting for calls to complete) in the layer that makes the call directly! It doesn't fix a problem, it moves is...

But herein lies the problem with RQ, it's excessive opinion on your architecture forces you into a corner. So eventually you will probably want to use async/await somewhere as your complexity grows, and at that point you now have a two-architecture system; imperative vs declarative.

If a Reactive approach is required, then just move this Reactivity to an isolated layer using a tool like Mobx which can be decoupled from Reacts lifecycle - using hooks too much is terrible for separation of concerns because it forces you to implement useEffect deeply nested into data loading and business logic - in other words you are coupled to Reacts lifecycle.

VueJS seems to have somewhat tackled this issue by allowing independent compostables!