Getting params in wrapped/nested routes

import { Outlet } from "solid-app-router";

function PageWrapper () {
  return <div>
    <h1> We love our users! </h1>
    <Outlet/>
    <Link href="/">Back Home</Link>
  </div>
}

<Route path="/users" element={<PageWrapper/>}>
  <Route path="/" element={<Users/>} />
  <Route path="/:id" element={<User/>} />
</Route>

In this example, it seems that there is no way to get the “id” parameter from within the PageWrapper component. This is, as far as I can tell, due to parameters not being held by the global Router context, but rather the local Route context. Are there any workarounds for this?

[EthanYidong]

If this is not intended, I am open to creating a pull request for this, however, changing the current behavior of useParams to pull from the global router may break some code which expects to only get parameters from the current Route context provider. To avoid that, should I create a new function such as useGlobalParams?

[ryansolid]

Any one interested in this willing do a little leg work for me? We made a choice that seemed sensible, mostly that this decision might lead us to a path where we’d need to reactively account for things that don’t exist. Ie… have to use proxies. Seemed sort of dangerously leaky. But I’d consider it if this was pretty standard. So do other client routers allow this?

The next thing I’d be doing is looking at React Router, Tanstack Router, Next Router, Sveltekit Router, Nuxt Router, etc… and determining if they had this functionality.