Expose the entire router state in data function about solid-router HOT 3 CLOSED

I think this is reasonable. Especially now that I've hoisted it and router levels are no more than index used to resolve nested Routes. I had different behavior since I constructed params differently. And now that I've hoisted it above as you say you can't access that context. Which is an interesting point on it's own as it means the router needs to be the lowest global context, if you want to be able to read from context above it. It also mean data functions are outside of the tree so they can't leverage any nested contexts. I realized this while implementing and I'm not sure there is much to do for it since to parallelize nested we need to do this. With this setup we can navigate to..
users/123/settings and load both the user page and the user settings sub page in parallel while loading the data for both in parallel as well.

It does leave some questions on cascading data loads. Like what if the settings doesn't have enough from the url to know what data it needs, and needs to wait for the parents data to load first. In that case though I guess you wouldn't bother with a nested data component since you can't fetch in parallel anyway. Basically the view hierarchy can communicate to each other through props on the Route component or Context, but the data hierarchy has no similar way to communicate now that i've hoisted it. And in fact outside of a global store or props cannot communicate its results (nested contexts aren't available). These restrictions seem mostly fine but I feel like we can do better.

The answer might be related to this suggestion. Anything stored on the router itself would form a singleton context of sorts. But cleanup might be obvious. Anyway this is the sort of thing I'm thinking about.

from solid-router.

Ok done in 0.0.33. Also add NavLink and isActive

from solid-router.

Aweesome! Thank you Ryan, that'll be really helpful!

from solid-router.