This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-04
Channels
- # aleph (2)
- # beginners (80)
- # boot (18)
- # cider (6)
- # cljs-dev (14)
- # cljsrn (5)
- # clojure (114)
- # clojure-android (5)
- # clojure-dev (8)
- # clojure-greece (6)
- # clojure-italy (9)
- # clojure-russia (108)
- # clojure-uk (82)
- # clojurescript (158)
- # css (1)
- # cursive (21)
- # data-science (1)
- # datomic (66)
- # emacs (9)
- # ethereum (3)
- # fulcro (26)
- # graphql (7)
- # hoplon (25)
- # juxt (2)
- # keechma (34)
- # lein-figwheel (4)
- # leiningen (2)
- # off-topic (4)
- # om (5)
- # onyx (14)
- # parinfer (2)
- # pedestal (17)
- # planck (3)
- # portkey (14)
- # re-frame (23)
- # reagent (12)
- # ring (8)
- # rum (1)
- # shadow-cljs (506)
- # spacemacs (2)
- # vim (11)
- # yada (6)
hey everyone. does pedestal out of the box support interceptors scoped by request method and not by verb map ? cant find anything in docs on that regard ..
["/:id" ^{:interceptors [load-order-from-db]}
{:get view-order
:put [put-only-intc update-order]}]
["/:id" :get [load-order-from-db view-order]]
["/:id" :put [load-order-from-db put-only-intc update-order]]
and also can i provide handlers as vars so they are resolved dynamically and i need not to restart pedestal each time i change logic inside of a handler ?
The usual way to do that is by providing the route table as a var, not just the handlers. One sec & I can find a link.