react-query-questions
solid-query-questions
table-questions
virtual-questions
router-questions
react-charts-questions
ranger-questions
vue-query-questions
svelte-query-questions
bling-questions
form-questions
angular-query-questions
start-questions
db-questions
start-showcase
router-showcase
📣-announcements
Infinite params (using route.navigate)
/$type/$id/path/to/a/directory
The infinite params are extracted from the fullPath (using useRouter().state.currentLocation by removing the route's matched path. How can I use route.navigate() by adding a different subpath ? (or there is a way to match typed recurring params ?)...Pending components being rendered based on the tree's hierachy from the root route
Pending Component at the rootRoute level, so it'd be used for all its child pages unless a child route has a pendingComponent defined.
At the moment, a pendingComponent at the rootRoute level does NOT seem to work.
Rather, this is what I've currently found to be what works....Possible to go back with the Link component?

Can you edit a title via TanStack Router?
routerState doesn't work in return of rootRoute component
'routerState' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.
Removing the condition in the return makes the error disappear and routerState is typed correctly....
Should updating search params always cause a re-render?
navigate to change search params, the URL is updating but the app is not re-rendering with the latest values. This seems like maybe a bug, or maybe I'm missing something fundamental?
If I then take some other action, the next re-render will pick up the latest values, FWIW....Default search params on initial render
preSearchFilters doesn't seem to set default values. Related discussion from react-location here: https://github.com/TanStack/router/discussions/143#discussioncomment-1775952
Any way to set initial defaults? I guess I could navigate (with replace:true) in an effect but then I guess I would have to make all the params optional (given they won't exist on the initial render)....Redirecting on log out
logout function provided by react-query-auth. It is changing the URL to /login, but not rendering the component specified by my login route. Leaving the screen and coming back, or refreshing forces the login component to render.
I'm doing this via a guard like:
```js
export default function AuthGuard({ children }: { children: React.ReactNode }) {...Next.js has made me soft
what is the idiomatic way to compose routers?
storybook support?
Link state prop
type of `Link to` is any
<Link to='/'>Home</Link>
// ^ (property) to?: any
<Link to='/'>Home</Link>
// ^ (property) to?: any

About to give up, trying to use simple Link component with but it won't work.

Prevent loader from rerunning
what is Hierarchical 3-stage search param manipulation?
Hierarchical 3-stage search param manipulation, but I have no idea what it is. is it related with ecmascript stage-3?Using TRPC's react-query hooks in router
How to define a 404 or not found page?
Incremental adoption guide
How to handle anchors via router