Recursive Data Fetching

[jaredpalmer]

We would need to walk the tree 🚶‍♀️

[mjackson]

You basically just need to figure out which components you're planning to render, go fetch all their props, and then provide them to the components, right? I already did this back in earlier versions of RR. Would be happy to take a stab at it again here :D

[jaredpalmer]

Yeah the would be awesome.

[jaredpalmer]

On this note, have a gut feeling that the solution could be very useful if we wanted do a static export like gatsby (but obviously without the graphql complexity)

[mohsen1]

You basically just need to figure out which components you're planning to render

Rendering once to figure out what data needs to be fetched is something I did before. Not clean but it works. Only if React render could return a promise... 😬

[tamagokun]

I've used this in the past to accomplish data fetching for any component in a tree on the server: https://github.com/ctrlplusb/react-tree-walker

Worked out really well.

[jaredpalmer]

Yeah that could work.

@mjackson is react-router-config matchRoutes recursive? Should we be using that instead of the current implementation?

[benkingcode]

@jaredpalmer I actually just implemented this in a project I'm working on, I've published it as an npm package, might be of help!

https://github.com/dbbk/react-data-fetching-components