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
Hello! I adapted your data-driven-dependencies example to work with nextjs 13 and wanted to get your feedback on whether certain design choices make sense. Long story short, this method uses the same network cache strategy to convert the pre-fetched data into a preloaded query. So far, it seems to work? But I appreciate any insight you have. And thanks for all your hard work!
The big questions I have are:
(i) whether exposing the network cache by shoehorning it onto the relay network would cause any ill side effects, including even when wrapped in useMemo, and;
(ii) whether there is a better way to pass the preloaded query to the client component through the hydrator other than by wrapping the client component with a context provider.
Hello! I adapted your
data-driven-dependencies
example to work with nextjs 13 and wanted to get your feedback on whether certain design choices make sense. Long story short, this method uses the same network cache strategy to convert the pre-fetched data into a preloaded query. So far, it seems to work? But I appreciate any insight you have. And thanks for all your hard work!The big questions I have are:
(i) whether exposing the network cache by shoehorning it onto the relay network would cause any ill side effects, including even when wrapped in useMemo, and;
(ii) whether there is a better way to pass the preloaded query to the client component through the hydrator other than by wrapping the client component with a context provider.
Thanks again!
https://gist.github.com/litewarp/cc64c7624cad5702923aef62fcb2ff31
The text was updated successfully, but these errors were encountered: