This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-15
Channels
- # aws-lambda (3)
- # beginners (37)
- # boot (294)
- # carry (1)
- # cider (38)
- # cljs-dev (37)
- # cljsjs (88)
- # clojure (187)
- # clojure-android (2)
- # clojure-austin (1)
- # clojure-dusseldorf (9)
- # clojure-hk (3)
- # clojure-italy (12)
- # clojure-russia (36)
- # clojure-spec (55)
- # clojure-uk (27)
- # clojurescript (75)
- # community-development (5)
- # conf-proposals (2)
- # copenhagen-clojurians (3)
- # cursive (9)
- # datomic (54)
- # devcards (5)
- # devops (3)
- # dirac (69)
- # emacs (6)
- # ethereum (1)
- # euroclojure (1)
- # events (3)
- # funcool (1)
- # hoplon (20)
- # immutant (4)
- # luminus (14)
- # midje (4)
- # om (178)
- # om-next (2)
- # onyx (47)
- # pedestal (19)
- # protorepl (20)
- # re-frame (14)
- # reagent (54)
- # ring (2)
- # ring-swagger (7)
- # test-check (10)
- # uncomplicate (11)
- # untangled (9)
- # yada (9)
@niwinz Any plans to have cool clojure.spec integration with catacumba requests? Right now I am using a multi-spec
that dispatches on the :path
in the context and, if the request is valid, delegates to the next handler, otherwise sends a 400 bad request.
I imagine a tighter integration though -- possible through metadata or as the second or fourth param in a route. For example,
[[:prefix "api"
^{:catacumba/validate ::my-spec} [:get "foo" #'handlers/foo]]]
;; or
[[:prefix "api"
[:get ::myspec "foo" #'handlers/foo]]]
;;or
[[:prefix "api"
[:get "foo" ::myspec #'handlers/foo]]]
Thoughts?