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
Best approach for navigation back and forward?
/posts
- /posts/1 is a single post page which has 'back' link inside
If there would be no such a button, user would be forced to use browser navigation which would go back to the previous page (not push another route). As far as I understand, I can use history.go(-1), but if user has just directly opened the /posts/1 page , that would redirect him to the page he initialy came from. Of course I can pass some search params like backURL, but the downside of this is that it pushes a new route to the history. Is there something like in-app router history, that would remember the previous in-app pages?
I hope it's not a stupid question 🙂...Root loader with notFound throws suspense error
Opting out of parent layout(s) in child route?
Loader not waiting for all async operations
await.
Example:
```typescript
...Parallel routes/named outlets
No routeTree.gen.ts file

make trailing slashes configurable
/foo/, the server will serve the correct SPA, but then TanStack router takes away the trailing slash, leaving /foo. If the user then re-loads the page, we're seeing a server-side redirect from django again towards /foo/, and then the router takes the slash away again....using tanstack router inside react router
parent is undefined

Redirect to relative path does redirect to wrong path
Link from getRouteApi
Context is not up to date after navigate
/dashboard after the successful login.
My /dashboard route is a protected route, I can access it only if context.useris not null. ...Different Suspense behaviour depending on where a user comes from
Suspense component around Route /a:...Error: Redirecting from parent to child on load
Loader in parent route runs again if only a new child route is rendered
dashboard.tsx only runs once if user navigates from dashboard.users.tsx to dashboard.roles.tsx ? But it doesn't. How can i possibly achieve this with file based routing?Using `navigate` in a providers handler before RouterProvider instance
Layout route with `routeFilePrefix `
routeFilePrefix?
I have following folder structure?...Confirm when user press the back button of browser
Can we have different types for search params input and output?
<Link to="/" search={{page: 1}} /> // <-- input is the arguments we pass to the `search` prop
<Link to="/" search={{page: 1}} /> // <-- input is the arguments we pass to the `search` prop