Feature: detect mismatched route parameters at compile time

[Diggsey]

At the moment, the route handler will panic if it can't find a matching name for a route parameter, with the error Unable to match url parameter name ....

It would be an improvement if the router macro caught this at compile time.

[tomaka]

The panicking shouldn't happen.

[tommilligan]

Are you using string-style invocation? The docs state:

When using URL parameters with string-style syntax, the parameter names in the URL and identity: type pairs must be the same, e.g. ... ["/users/{name}", name: String] ... . This can't be checked at compile time so bad route definitions will cause a runtime panic.

If not, could you provide a minimal example?

[Diggsey]

Sorry yes I should have made that clear. This feature request is to check that at compile time, which is definitely possible given the stabilisation of procedural macros and other meta-programming features.