This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-04
Channels
- # beginners (14)
- # boot (28)
- # chestnut (9)
- # cljsrn (18)
- # clojure (64)
- # clojure-conj (1)
- # clojure-dusseldorf (45)
- # clojure-finland (4)
- # clojure-gamedev (1)
- # clojure-greece (8)
- # clojure-italy (22)
- # clojure-russia (4)
- # clojure-spec (19)
- # clojure-uk (38)
- # clojurescript (49)
- # code-reviews (2)
- # component (12)
- # core-async (3)
- # cursive (3)
- # data-science (2)
- # events (4)
- # fulcro (394)
- # heroku (3)
- # hoplon (16)
- # immutant (11)
- # jobs (5)
- # lein-figwheel (1)
- # lumo (18)
- # off-topic (8)
- # om (11)
- # other-languages (1)
- # overtone (1)
- # pedestal (7)
- # portkey (62)
- # protorepl (1)
- # re-frame (40)
- # reagent (41)
- # ring-swagger (5)
- # spacemacs (5)
- # unrepl (5)
- # yada (12)
Hi, I’,m just getting into vase and I’m wondering how schema updates are managed. It looks like conformity is being used to manage transacting in the norms. So, now if I add some new attributes to :myservice/my-schema
they aren’t transacted in
Hey, I wonder if there is any debugging interceptor/middleware for pedestal? I mean showing always request body, params, headers etc?
+ status, timing, method etc
should i just make intereceptor which will print request value?
The default log-request
(https://github.com/pedestal/pedestal/blob/master/service/src/io/pedestal/http.clj#L80) could maybe have a debug or trace clause to spit the whole request data. Maybe it doesn’t to avoid leaking sensitive information on misconfigured services?