Support for nested routes about react-resource-router HOT 4 OPEN

There are few reasons to keep this router "flat", predictability(or discoverability) is one of them.

Recently we implemented nested routes for "flat" router using pregeneration for routing table:

• every layout can have a named slot for one (or more) injected children
• so these props are just added into routing table, and then passed to the Layout component
  • recursively

Technically speaking there is no difference between this and navigation example - every route record can hold as much information as needed, including all component to be rendered as "nested routes" and all their props as well.

from react-resource-router.

Thanks! I think the issue I have with flat routing conceptually is that routing is a very "hierarchical" concept, and flat routing hides that hierarchy. I could potentially (as I think you've suggested) write my routes hierarchically and then use a function to flatten them out. It's not a great solution but I can understand if you feel that flat routing is a core idea of this router.

from react-resource-router.

It's more about two different metal models forming the base requirements. Let's imagine you want to defer transition to a new page until "some" stuff is loaded (like in old non-SPA sites or NextJS):

• (relay and nested routes). useTranstion + Suspense, call it a day
• (flat router) get information about route target, preload everything required, then perform the transition.

The outcome is (almost) the same, but realizations are different. And it order to support this, and many other patterns, without not yet production-ready Concurrent Mode you might need flat routing.

And here we are. Well, will be

from react-resource-router.

That makes sense! Thanks for taking the time to explain.

from react-resource-router.