Pathless layout routes in new alpha version

[KaRkY]

I have been testing alpha version of router and I would like to know how can I make multiple pathless layout routes on same level.
Example:

createRouteConfig({ element: <RootLayout /> }).addChildren((createRoute) => [
  createRoute({ path: "/", element: <LandingLayout /> }).addChildren((createRoute) => [
    createRoute({ path: "/", element: <LandingPage /> }),
  ]),
  createRoute({ path: "/", element: <AuthenticationLayout /> }).addChildren((createRoute) => [
    createRoute({ path: "signin", element: <span>Login</span> }),
    createRoute({ path: "signup", element: <span>Register</span> }),
  ]),
  createRoute({ path: "users", element: <UsersLayout /> }).addChildren((createRoute) => [
    createRoute({ path: "/", element: <UsersPage /> }),
    createRoute({ path: ":id", element: <UserPage /> }),
  ]),
  createRoute({ path: "*", element: <span>404</span> }),
])

[tannerlinsley]

This is on my todo list. Very high priority. I believe it will be as easy as passing path: false :)

[tannerlinsley]

Just finished adding this functionality. You'll be able to omit the path of the route and add an id:

createRoute({ id: 'unique-id', element: <Anything />, loader: () => {...} }).addChildren(...)

[KaRkY]

Nice I can confirm that it works but now I found problems with Link and Mantine polymorphic components. Typescript complains that search and params are missing. Both of their type deffinition looks like () => never. I don't know if it's router problem or Mantine.

<Text component={match.Link} to="/">Testing</Text>

Type '{ children: string; component: <TTo extends string = ".">(props: { to?: ToPathOption<AllRouteInfo<RouteConfig<"__root__", string, string, "", AnyLoaderData, {}, unknown, unknown, {}, AnySearchSchema, {}, {}, Record<...>, {}, (RouteConfig<...> | ... 2 more ... | RouteConfig<...>)[]>>, "", TTo> | undefined; hash?: Upd...' is missing the following properties from type 'Omit<{ to?: string | undefined; hash?: Updater<string, string> | undefined; from?: "" | undefined; } & { search: (current: {}) => never; } & { params: (current: {}) => never; } & { ...; } & ... 4 more ... & { ...; }, "component" | keyof TextProps>': search, params

Should I create and issue?

[tannerlinsley]

I see it too. Working on a fix Tanner Linsley Sent with Spark

…

On Oct 21, 2022 at 4:07 AM -0600, Rene Svetina ***@***.***>, wrote: Nice I can confirm that it works but now I found problems with Link and Mantine polymorphic components. Typescript complains that search and params are missing. Both of their type deffinition looks like () => never. I don't know if it's router problem or Mantine. <Text component={match.Link} to="/">Testing</Text> Type '{ children: string; component: <TTo extends string = ".">(props: { to?: ToPathOption<AllRouteInfo<RouteConfig<"__root__", string, string, "", AnyLoaderData, {}, unknown, unknown, {}, AnySearchSchema, {}, {}, Record<...>, {}, (RouteConfig<...> | ... 2 more ... | RouteConfig<...>)[]>>, "", TTo> | undefined; hash?: Upd...' is missing the following properties from type 'Omit<{ to?: string | undefined; hash?: Updater<string, string> | undefined; from?: "" | undefined; } & { search: (current: {}) => never; } & { params: (current: {}) => never; } & { ...; } & ... 4 more ... & { ...; }, "component" | keyof TextProps>': search, params — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[sojib-lowp]

@tannerlinsley
Is it somehow possible to implement this in a file based routing system?