@ikitommi I supply the routes in the order you mentioned and use :conflicts nil as config. Will this result in a router which offers he maximum performance possible? I have about 150 groups of routes. Besides Patient I have 150 other paths. Each “group” has 6 routes. So there will be about 900 routes.

the best performance is if the routes don't conflict

@ikitommi i have parameters spec'd as (coll-of pos-int?), but this displays in swagger-ui's example as [0] which is obviously not a valid value. spec generators can make correct example sequences out of the spec. any idea what could be causing this?

@akiel only the conflicting routes are served with linear router, other with best possible algo. There is one extra method call in the stack, so maybe a few ns penalty.

@vale does the swagger json contain :min value? Should be 1 for pos-int? I believe...

Is it possible to have nested routes that have gets on them?

I.E.

["/user"
    {:get  {:summary    "get a user"
            :middleware [middleware/wrap-restricted]
            :handler    (fn [req]
                          (user/get-user req))}}
    ["/login"
      :post {:summary    "login as user"
             :parameters {:body {:screen_name    string?
                                 :password string?}}
             :handler    (fn [req]
                           (user/login req))}}]
...

I'm getting a 404 for /user

@jonwalch see https://github.com/metosin/reitit/issues/175

thanks! Perfectly fine using the existing syntax