"articles/:id<[0-9]+>.:format" gives 2 tokens: - NonDotRouteToken("articles", false, None) - DotRouteToken(Seq(NonDotRouteToken("id", true, Some("[0-9]+".r)), NonDotRouteToken("format", true, None)))
"articles/:id<[0-9]+>" gives 2 tokens: - NonDotRouteToken("articles", false, None) - NonDotRouteToken("id", true, Some("[0-9]+".r))
Routes are sorted reveresly by the number of placeholders because we want to fill as many placeholders as possible.
Routes are grouped by methods.
"websocket" and "cookieNeeded" members are named after SockJS options, ex: {"websocket": true, "cookie_needed": false, "origins": ["*:*"], "entropy": 123}
"websocket" and "cookieNeeded" members are named after SockJS options, ex: {"websocket": true, "cookie_needed": false, "origins": ["*:*"], "entropy": 123}
- websocket: true means WebSocket is enabled - cookieNeeded: true means load balancers needs JSESSION cookie
Easy-to-remember path to Swagger UI: /xitrum/swagger
Scan all classes to collect routes from actions.
https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md
Routes are grouped by methods. The routes are
ArrayBuffer
so that routes can be modified after collected.