Routing precedence / React-Router route ranking issue

[KnisterPeter]

Hi,

we have a conflict (precedence problem) in one of our routes.
For example we have to routes like this:

/routes
 \- $var.tsx
 \- order.tsx

Is there a way that /order will be preferred during route decision? Currently we see that the /$var route will be called for every request done.

Thanks for any advice.

[KnisterPeter]

To make it a bit more concrete:
This is the output of remix routes in our app:

<Routes>
  <Route file="root.tsx">
    <Route path=":owner/:repo/build/:buildId/log" file="routes/$owner/$repo/build/$buildId.log.ts" />
    <Route path="api/:org/:repo/build/:id/result" file="routes/api/$org.$repo.build.$id.result.ts" />
    <Route path=":owner/:repo/build/:buildId" file="routes/$owner/$repo/build/$buildId.tsx" />
    <Route path=":owner/:repo" index file="routes/$owner/$repo/index.tsx" />
    <Route path="api/authenticate" file="routes/api/authenticate.ts" />
    <Route path="api/webhook" file="routes/api/webhook.ts" />
    <Route path="_docs/*" file="routes/_docs/$.tsx" />
    <Route index file="routes/index.tsx" />
  </Route>
</Routes>

The route _docs/something is never taken but :owner/:repo is used instead.
According to the docs of react-router this is wrong, but I'm not sure what we did wrong here.

[KnisterPeter]

React Routers ranking algorithm runs into an issue in our case:

• The route _docs/* gets a value of 10
  • 2 segments => 2
  • spat penalty => -2
  • static part => +10
  • in total this is 10
• The route :owner/:repo get a value of 10
  • 2 segments => 2
  • 2 dynamic parts => +3 each
  • index route => +2
  • in total this is 10

Now the order in the file system defines the selected match (file based routing).

[KnisterPeter]

Making the :owner/:repo route a non-index route results in other problems during routing, as the routes below it would then require the :owner/:repo route to render an <Outlet /> which it shouldn't as there is no shared UI.

Is this a workaround? Is this an issue in react-router and should we create an issue over there?