@vale the conflict resolution is a 1-arity fn, so (constantly nil) will do too. Changed the options merging so nil works in the next version, you can try [metosin/reitit "0.1.4-SNAPSHOT"].

also added route name conflict resolution, which can’t be switched off.

swagger-apis don’t need the [:swagger :id], in most cases, there is only one swagger api within a router, so we infer the id to :reitit.swagger/default. One line less to type…

I’m thinking that we could push a reitit-middleware module with some common data-driven middleware packaged. optional, but make starting with reitit-ring easier.

• body-parsing (dependency to muuntaja) • multipart (ported from ring) • exception-handling (ported from compojure-api). Just enough batteries & opinions to make starting easier. And should be mostly on par with features with compojure-api after that.

oh, btw, the metosin/reitit-frontend by @juhoteperi seems to be in the latest SNAPSHOT too. No docs apparently yet, but examples: https://github.com/metosin/reitit/tree/master/examples/frontend & https://github.com/metosin/reitit/tree/master/examples/frontend-controllers. 👍