app.http controllers evaluation is in alphabetical order, causing problem with optional params

[danbord]

Given the following controller declarations:

app.http("accounts", {...,  route: "accounts/{accountId?}/{action?}"})
app.http("products", {...,  route: "accounts/{accountId?}/products/{productId?}"})

If we GET from the following url : /api/accounts/12345/products/ it will end up in the accounts controller with param action="products"

Expected behavior

When evaluating a route, I think the static params should have precedence over the optional ones. Now they are evaluated in alphabetical order (which seems nonsense)

Known workarounds

If we rename the accounts controller "zaccount" (to put after the "products" alphabetical position when evaluating the route). Then its gonna be evaluated first. And both controllers works as planned.

[timtucker-dte]

Presumably this should follow the same order of preference as ASP. Net routing used for. Net functions:
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-9.0#rtp

[danbord]

Net routing used for. Net functions:

Totally agree with that, thanks for the reference