Route Confusion

[apoliakov]

Reported by a user. A route/:arg can be confused with route/otheroption and cause hard-to-predict behavior. Both methods get called. For example given:

  @GetApi('/greeting/:user')
  static async oneGreeting(ctxt: HandlerContext, @ArgSource(ArgSources.URL) user: string) {
    ctxt.logger.info(`Called greeting ${user}`);
    return "thanks!"
  }

  @GetApi('/greeting/foo')
  static async anotherGreeting(ctxt: HandlerContext) {
    ctxt.logger.info(`Called the other greeting with foo`);
    return "thanks much!"
  }

If we run

curl http://localhost:3000/greeting/foo
thanks!

While the log says

2024-12-06 00:28:11 [info]: Called greeting foo 
2024-12-06 00:28:11 [info]: Called the other greeting with foo 

User who found this believes that we should error when building the app, if such a conflict is present.