Prefetching on routing example about react-query

[tannerlinsley]

Yeah it seems tooling hasn’t really caught up just yet. This is an interesting thread with some of my thoughts on this: https://twitter.com/tannerlinsley/status/1194976554553446403?s=21 Tanner Linsley

…

On Nov 20, 2019, 9:48 PM -0700, Thibaut Tiberghien ***@***.***>, wrote: Yes, it's a great start for sure. That would cover prefetching on user interaction, I was hoping to find something on routing events. Maybe some more declarative prefetching depending on location change? Not sure if react-router (or others) as builtin stuff to handle this. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[tannerlinsley]

You bet!

[tannerlinsley]

Did you see the suspense example in this repo? Tanner Linsley

…

On Nov 20, 2019, 9:16 PM -0700, Thibaut Tiberghien ***@***.***>, wrote: Hi! I am amazed by the work that went into this and thankful for having a fetching / caching / suspense library that is independent of the fetching mechanism used. Thank you 🙇. I know this is not really strictly react-query's land, but would you happen to have an example of prefetching on routing? Maybe with react-router or similar. I'm really tempted by your teasing of fetch-as-you-render which is also described in the react docs. I have read through this discussion in the react-router repo, but it's pretty hard getting a clear example / demo out of it 😬. So trying my luck in case anyone happen to have tried this already. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[tibotiber]

Yes, it's a great start for sure. That would cover prefetching on user interaction, I was hoping to find something on routing events. Maybe some more declarative prefetching depending on location change? Not sure if react-router (or others) as builtin stuff to handle this.

[tibotiber]

Agreed, that’s a good thread and we’re gonna need to wait and see what’s cooking in the routing world. I’d be happy with a Route that let’s me define a prefetch function prop along with the component or render prop. What do you think about this approach? Wouldn’t this work at runtime and avoid having to define data requirements at build time? You just want to call prefetch at the same time as you request your new “page” bundle no?

[tannerlinsley]

Yes that would work, but if you code split any of your routing logic, now you get a waterfall effect Tanner Linsley

…

On Nov 21, 2019, 1:19 AM -0700, Thibaut Tiberghien ***@***.***>, wrote: Agreed, that’s a good thread and we’re gonna need to wait and see what’s cooking in the routing world. I’d be happy with a Route that let’s me define a prefetch function prop along with the component or render prop. What do you think about this approach? Wouldn’t this work at runtime and avoid having to define data requirements at build time? You just want to call prefetch at the same time as you request your new “page” bundle no? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[tibotiber]

Right! Thanks for pointing that out, and for sharing your thoughts on this. Hope this thread can be useful to others. And feel free to close when you wish :).