This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-21
Channels
- # beginners (55)
- # cider (13)
- # cljdoc (4)
- # cljsjs (1)
- # clojure (11)
- # clojure-spec (7)
- # clojure-uk (9)
- # clojurescript (42)
- # docs (5)
- # figwheel-main (9)
- # fulcro (4)
- # graphql (4)
- # hoplon (27)
- # keechma (32)
- # leiningen (11)
- # luminus (2)
- # nyc (2)
- # off-topic (73)
- # parinfer (1)
- # re-frame (36)
- # reagent (2)
- # reitit (6)
- # ring-swagger (3)
- # shadow-cljs (51)
- # spacemacs (4)
- # tools-deps (17)
- # uncomplicate (1)
@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"]
.
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. 👍