Query Chain about farfetched HOT 4 OPEN

Seems like a pretty neat idea. But why is there a need for a dedicated operator? This seems like something a simple wrapper around allSettled would resolve.

const postLoadedRoute = chainRoute({
  route: postRoute,
  beforeOpen: {
    effect: createEffect(async () => await allSettled(profileQuery.start)),
  },
});

from farfetched.

Looks like we need allSettled without scopes in effector itself

from farfetched.

It is noteworthy that only queries are tracked, that is, there is no implicit transparency.
This loosens things up a bit, giving you the certainty you need in the complex concept of transitioning through routes. "This is a query and it will lengthen the wait, this is just a connected effect with analytics and it will work in the background."

from farfetched.

I truly agree that allSettled without scope would be great 👍

However, I have to mention that allSettled cannot solve all cases of chained queries.

For example, in some cases, we can open a page after some essential queries and load other data after navigation. In can be solved by some parameters of queryChain, but plain allSettled cannot solve this case. So, in my mind, allSettled definitely would be pretty useful as a part internal implementation of queryChain.

from farfetched.