Route ordering for static vs dynamic segments

[adrianncovaci]

When defining routes, it appears that the order of route registration is critical when mixing static and dynamic path segments. For example, having a dynamic route like /a/b/:id before a static route /a/b/c causes the router to match the dynamic route first, capturing c as the :id parameter instead of routing to the static path.

// This fails - dynamic route shadows static route
<Route path="/properties/lease/:id" view=EditView />
<Route path="/properties/lease/invoice-monitoring" view=MonitoringView />

// This works - static route declared first
<Route path="/properties/lease/invoice-monitoring" view=MonitoringView />
<Route path="/properties/lease/:id" view=EditView />

Is this expected? Shouldn't we handle the more specific routes first?

[gbj]

The router used to (in 0.6 and prior) have a scoring mechanism that tried to pick the most specific route. This mostly just added a bunch of overhead, in binary size and runtime.

Now, it simply matches the first matching route — once it has found a route that matches it stops looking for other matches.