This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-19
Channels
- # adventofcode (44)
- # announcements (2)
- # aws (9)
- # beginners (166)
- # braveandtrue (16)
- # calva (170)
- # cider (14)
- # cljdoc (9)
- # cljs-dev (4)
- # cljsrn (1)
- # clojars (1)
- # clojure (150)
- # clojure-dev (15)
- # clojure-europe (4)
- # clojure-india (3)
- # clojure-italy (93)
- # clojure-nl (18)
- # clojure-serbia (1)
- # clojure-spec (5)
- # clojure-uk (45)
- # clojurescript (54)
- # cursive (19)
- # data-science (8)
- # datomic (83)
- # emacs (6)
- # events (1)
- # hoplon (3)
- # hyperfiddle (3)
- # jobs (6)
- # jobs-discuss (1)
- # klipse (1)
- # lein-figwheel (6)
- # leiningen (15)
- # lumo (1)
- # nrepl (1)
- # pedestal (15)
- # re-frame (48)
- # reagent (4)
- # reitit (2)
- # remote-jobs (1)
- # rum (2)
- # shadow-cljs (111)
- # spacemacs (10)
- # sql (16)
- # testing (10)
- # tools-deps (5)
now that we’re trying to upgrade from 0.5.3 to 0.5.5 we’re running into https://github.com/pedestal/pedestal/pull/544/files#diff-c7e8051a2ca9de05fbfd6b4fc858ddc7. We’ve previously just enqueued map values as interceptors (which worked fine) but now the pre condition fails.
but looks like this was never intended. Would there be interest in accepting a change which makes enqueue also take values and converts them into an interceptor record?
if not maybe we should update the interceptors guide http://pedestal.io/reference/interceptors and change the code to produce interceptor records?
Yep, that is the intended behavior. We want to avoid interceptor xform and validation during chain execution.
https://github.com/nextjournal/pedestal/commit/a5b69d376a30f8baefa1695789eaec7bf2144eed
You may want to vote for https://dev.clojure.org/jira/browse/CLJ-1473 to ensure that malformed pre/post conditions aren't silently skipped
@martinklepsch I want them to be skipped because they break my app 😼