You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm using createBrowserRouter and I notice that if I have shouldRevalidate set to false (shouldRevalidate: () => false,) for a route's loader, I am unable to manually trigger a revalidation of a loader's data with revalidator.revalidate(); using the useRevalidator hook. Is this the intended behaviour? I don't want my route to automatically revalidate because I'm using searchParams and it leads to multiple firings of the loader, but then if I disable it the revalidate fn just doesn't execute.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm using createBrowserRouter and I notice that if I have shouldRevalidate set to false (
shouldRevalidate: () => false,
) for a route's loader, I am unable to manually trigger a revalidation of a loader's data withrevalidator.revalidate();
using the useRevalidator hook. Is this the intended behaviour? I don't want my route to automatically revalidate because I'm using searchParams and it leads to multiple firings of the loader, but then if I disable it the revalidate fn just doesn't execute.Beta Was this translation helpful? Give feedback.
All reactions