Separation of jester routes between different modules or files.

[ray-delossantos]

Hello:

I would like to divide a rest api project with jester into different src files:

Ex:
main.nim

    import jester, asyncdispatch
    import another_part
    routes:
      get "/":
        resp """ {"status": "ok"} """, "application/json"

another_part.nim

    import jester, asyncdispatch
    routes:
      get "/anotherpart":
        resp """ {"status": "ok"} """, "application/json"

The current behaviour is that on running like this it will try to open two web servers with the same port.

[dom96]

Thanks!

[0x1eef]

sinatra can be used to define a subclass that acts as a container for all routes defined inside it. the subclass can then be mounted to a namespace, like "/foobar" and then all paths defined within it become relative to /foobar. can jester do anything like that? if i understood this issue correctly, I guess not....

[PMunch]

This should be really easy to implement if we take most of the body out of the route macro and put it in a matcher macro without this line: https://github.com/dom96/jester/blob/master/jester.nim#L842 (and maybe a better way to name the matcher). Then the route macro can wrap that macro to get the matcher and add the serve call. This way you would be able to create multiple matchers which can then be baked into one manual matcher as seen in example 2.

[dom96]

Implemented. See alltest for details.