Revalidating a single loader (for realtime)

[barbinbrad]

In the supabase subscriptions example, we have something like this:

useSubscription(
    () => {
      fetcher.submit(null, { method: "post" });
    },
    { event: "INSERT", table: "clicks" }
  );

I believe that this is going to refetch all routes when a "click" is inserted. I think useRevalidator would do the same.

In the example, this is no problem -- but at scale -- this is a becomes a little more expensive. Sure we can define all types of business logic inside of shouldRevalidate -- but what would be really nice is if we had a mechanism to revalidate one route (like an action can post to one route). For me the really beautiful part about the loader is that it defines the "data requirements" of a route. If we could combine subscriptions with targeted revalidators, I think we could create some really nice UXs that aren't too heavy on the data fetching.

Here's what I was thinking:

const revalidator = useRevalidateRoute('/clicks');
useSubscription(
    () => {
      revalidator.revalidate();
    },
    { event: "INSERT", table: "clicks" }
  );

[nmackey]

I have an ask for something that I think is similar or may help solve this use case.

I would like an additional param added to shouldRevalidate that let's use know if it is being called as a result of the revalidate function from useRevalidator being triggered.

I have loaders that I only want to trigger when revalidate is called.

I'm currently achieving this by comparing current and next URLs and making sure they are the same and the rest of the params are undefined, however it seems like there should be a param that tells me shouldRevalidate is being triggered by the revalidate function.

[punkpeye]

@barbinbrad Have you ever found a solution for this?