Wildcard routes swallow later literals #1

New issue

Open

opened 2026-08-11 09:53:05 +00:00 by reviewer · 4 comments

reviewer commented

2026-08-11 09:53:05 +00:00

Owner

Declaring /files/*path before /files/health means the health route is never reached.

Minimal case:

let router = Router {
    Route("/files/*path")
    Route("/files/health")
}
router.match(URL(string: "https://x/files/health")!)  // matches the wildcard

I would expect the more specific pattern to win regardless of order.

Declaring `/files/*path` before `/files/health` means the health route is never reached. Minimal case: ```swift let router = Router { Route("/files/*path") Route("/files/health") } router.match(URL(string: "https://x/files/health")!) // matches the wildcard ``` I would expect the more specific pattern to win regardless of order.

reviewer added the

bug

label

2026-08-11 09:53:05 +00:00

reviewer commented

2026-08-11 09:53:06 +00:00

Author

Owner

Reproduced. The matcher returns the first route that matches at all, so order is load-bearing in a way nothing documents.

reviewer commented

2026-08-11 09:53:06 +00:00

Author

Owner

Scoring each match by specificity — literals beat parameters, parameters beat wildcards — and taking the highest. Draft on feature/route-priorities.

Scoring each match by specificity — literals beat parameters, parameters beat wildcards — and taking the highest. Draft on `feature/route-priorities`.

reviewer commented

2026-08-11 09:53:06 +00:00

Author

Owner

That reads well. One thought: two routes with the same score should keep declaration order rather than being arbitrary.