Async resource definition about react-resource-router HOT 3 CLOSED

I'll close this issue for now, if we have better ideas for the future happy to reopen :)

from react-resource-router.

This is an interesting idea. Needs some spiking as not entirely sure of the implications if we cannot immediately know the type and the getKey function. I'm especially thinking about hydration from SSR, where we pass the state directly to the router and expect useResource hooks to immediately render with data 🤔

from react-resource-router.

The resource chunk existence before the application start sounds not like a big problem for code splitting, however in this case it will be loaded with the full dataLoader as well, bringing more code than required initially.
Quite far from the perfect.

Sounds like writting a little more code is still a better idea.

from react-resource-router.