routeId should be based on route path instead of file name.

[adnanalbeda]

I'm trying React-Router Framework, and I tried to add my first route:

import { type RouteConfig, index, route } from "@react-router/dev/routes";

export default [
  index("./routes/home.tsx"),
  route("home", "./routes/home.tsx"), // Duplicate file
] satisfies RouteConfig;

Then I ran pnpm dev and got hit by error:

Error: Route config in "routes.ts" is invalid.

Error: Unable to define routes with duplicate route id: "routes/home"

So I discovered that route Ids are file based, instead of path based.
Technically, no one would use same file in more than one route, but it should be possible.
What's more unlikely is overriding route path or duplicating them.

So I tried this code:

import { type RouteConfig, index, route } from "@react-router/dev/routes";

export default [
  index("./routes/home.tsx"),
  route("home", "./routes/home2.tsx"),
  route("home", "./routes/home3.tsx"), // Duplicate route
] satisfies RouteConfig;

It had no issues running it, picked the first /home route home2, and doesn't override it.

So I guess it makes more sense to pick routeId from the route path instead of file based to avoid duplicating route path.

[sergiodxa]

Let's say you have:

layout(layoutFile, [
  route("home", homeFile, [
    index(indexFile)
  ])
])

All of that becomes /home

What's the route id of each layout route, the home route and the index route?

The file is more unique than the path as many routes can become the same path, and some routes may not even have a path (layouts and index)