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
I have a multi layout application where I fetch the data in one of the layout.
The data fetched in this layout is used with useRouteLoaderData in child components.
Since the documentation recommends using the useCachedLoaderData, is there a way similar where I can get the data similarly in useRouteLoaderData - possibly with useCachedRouteLoaderData ?
Thank you for your hard work on this package (and all the videos on YT too!).
The text was updated successfully, but these errors were encountered:
Just ran into a similar bottleneck... I just moved all my data fetching logic to a parent layout hoping I could utilize Remix's in-built context with useRouteLoaderData, but there's no cached version of route loader data with this library...
I really love the abstraction I get from using remix-client-cache, would be great to have something for sharing the cached data across children routes.
Hey guys, sorry for the very long wait! Let me ask you this first, if the data is cached and returned from the clientLoaders its made available through the context via useRouteLoaderData, I would expect it to work out of the box with it, is that not the case? What exactly happens?
I have a multi
layout
application where I fetch the data in one of the layout.The data fetched in this
layout
is used withuseRouteLoaderData
in child components.Since the documentation recommends using the
useCachedLoaderData
, is there a way similar where I can get the data similarly inuseRouteLoaderData
- possibly withuseCachedRouteLoaderData
?Thank you for your hard work on this package (and all the videos on YT too!).
The text was updated successfully, but these errors were encountered: