Help to understand the need to `getParentRoute`

Why is the need to use

getParentRoute

getParentRoute

when defining the

new Route()

new Route()

const indexRoute = new Route({
  getParentRoute: () => rootRoute,
  path: '/',
  component: () => {
    return (
      <div className="p-2">
        <h3>Welcome Home!</h3>
      </div>
    )
  },
});

const routeTree = rootRoute.addChildren([indexRoute])

const indexRoute = new Route({
  getParentRoute: () => rootRoute,
  path: '/',
  component: () => {
    return (
      <div className="p-2">
        <h3>Welcome Home!</h3>
      </div>
    )
  },
});

const routeTree = rootRoute.addChildren([indexRoute])

Since I'm adding

.addChildren

.addChildren

could that be inferred, like

indexRoute

indexRoute

after that point knows that its parent is the rootRoute?

TanStack•3y ago•

3 replies

urgent-maroon

Help to understand the need to `getParentRoute`

Why is the need to use

getParentRoute

getParentRoute

when defining the

new Route()

new Route()

const indexRoute = new Route({
  getParentRoute: () => rootRoute,
  path: '/',
  component: () => {
    return (
      <div className="p-2">
        <h3>Welcome Home!</h3>
      </div>
    )
  },
});

const routeTree = rootRoute.addChildren([indexRoute])

const indexRoute = new Route({
  getParentRoute: () => rootRoute,
  path: '/',
  component: () => {
    return (
      <div className="p-2">
        <h3>Welcome Home!</h3>
      </div>
    )
  },
});

const routeTree = rootRoute.addChildren([indexRoute])

Since I'm adding

.addChildren

.addChildren

could that be inferred, like

indexRoute

indexRoute

after that point knows that its parent is the rootRoute?

Help to understand the need to `getParentRoute`

Similar Threads

Help to understand the need to `getParentRoute`

Similar Threads

Similar Threads

Similar Threads