This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-27
Channels
- # beginners (29)
- # biff (4)
- # calva (3)
- # cider (5)
- # cljdoc (24)
- # clojure (40)
- # clojure-conj (6)
- # clojure-europe (17)
- # clojure-nl (1)
- # clojure-norway (20)
- # clojure-uk (10)
- # clojurescript (26)
- # core-typed (15)
- # cursive (8)
- # datomic (5)
- # figwheel-main (2)
- # honeysql (1)
- # hyperfiddle (77)
- # jobs-discuss (5)
- # joker (3)
- # malli (36)
- # missionary (18)
- # other-languages (9)
- # pedestal (7)
- # rdf (2)
- # shadow-cljs (6)
- # specter (4)
- # squint (12)
- # xtdb (7)
Interesting observation "if a handler returns a partial response map, Pedestal accepts it as is, even if missing the :header"
P.S. It can be hard to tell whether "allows...to omit headers" is the problem or the solution. Reading the details, I infer a pattern of naming enhancement issues as if to complete the sentence, "effective with this patch, the system ___"? If the house were on fire, the enhancement might be titled, "doesn't burn"?
also been burned by this several times
Yes, it’s an odd mix of excessive rigor in one place — detecting the :response map to terminate the interceptor chain) — vs. excessive slack elsewhere: ignoring a :response map that doesn’t match the expectation (which defies the intent of the developer), and allowing pretty much anything from a handler because the interceptor chain terminates when it runs out of interceptors.
I got hit by this the other day too.