This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-19
Channels
- # 100-days-of-code (12)
- # beginners (116)
- # calva (2)
- # cider (16)
- # cljdoc (5)
- # cljs-dev (26)
- # clojure (161)
- # clojure-italy (7)
- # clojure-nl (9)
- # clojure-spec (49)
- # clojure-uk (112)
- # clojurescript (50)
- # clojutre (4)
- # core-async (2)
- # cursive (4)
- # datomic (192)
- # emacs (10)
- # events (4)
- # figwheel-main (147)
- # fulcro (94)
- # graphql (5)
- # instaparse (1)
- # jobs-rus (1)
- # keechma (10)
- # leiningen (223)
- # luminus (3)
- # mount (23)
- # nrepl (8)
- # off-topic (44)
- # onyx (10)
- # pedestal (5)
- # re-frame (19)
- # reitit (8)
- # shadow-cljs (62)
- # uncomplicate (3)
I bit confused by something: how can an endpoint using spec coercion successfully run the coercion (I see it in debug breakpoints and debug messages), but the actual data delivered to the endpoint handler isn’t coerced? I tried manually putting :coercion reitit.coercion.spec/coercion
in the endpoint definition, but the :body-params
is still the uncoerced data.
@seantempesta the coerced parameters are under :parameters
in the request. The raw params are left untouched, e.g. :body-params
.
ahhhhhhh. well shit, now I feel stupid. thanks @ikitommi!
Afternoon. Is there some middleware or something that can turn query parameter keys into keywords like how body parameters are?