scorper routes

[sdmcallister]

I think it is interesting how you can define routes/handlers in (at least) two ways. Just wondering when someone might choose one over the other? Does having two options provide a benefit or create overhead when designing application? Wondering what others think.

I tend to favour the first form, but probably only because it seems more familiar.

proc handler(req: Request) {.async.} =    let headers = {"Content-type": "text/plain"}    await req.resp("Hello, World!", 
  headers.newHttpHeaders())

let r = newRouter[ScorperCallback]()  

r.addRoute(cb, "get", "/")

or

proc handler(req: Request) {.route("get","/one"),async.} = discard
let r = newRouter[ScorperCallback]()
r.addRoute(handler)

[bung87]

pragma style is mostly inspired from python's frameworks , the benefit is when you starting programming , let's say apis, you implement the interface proc and defines the route where the implementation is, so you no need move your focus to main proc , where the router is. this also allow you implements a library import to your program, has its interfaces and routes.

oh, I forget pragma style still need add proc to router manually , maybe in the future I can load all routes by specify the module name.

[bung87]

PR reflection.moduleSymbols nim-lang/Nim#9560 is perfect solution for this.

[bung87]

starting from v1.0.20, routermacros added mount macro , see https://github.com/bung87/scorper/blob/devel/tests/tmount.nim