This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-31
Channels
- # aleph (1)
- # announcements (2)
- # beginners (20)
- # calva (44)
- # cider (60)
- # clj-kondo (6)
- # clojure (27)
- # clojure-dev (2)
- # clojure-europe (8)
- # clojure-italy (18)
- # clojure-mexico (5)
- # clojure-nl (61)
- # clojure-spec (12)
- # clojure-uk (101)
- # clojurescript (82)
- # cursive (2)
- # data-science (21)
- # datomic (24)
- # fulcro (19)
- # graalvm (5)
- # hoplon (11)
- # jobs-discuss (35)
- # juxt (7)
- # keechma (6)
- # off-topic (21)
- # pedestal (5)
- # planck (2)
- # qa (43)
- # re-frame (3)
- # reagent (7)
- # reitit (4)
- # rewrite-clj (12)
- # sql (10)
- # testing (4)
- # tools-deps (6)
- # vim (23)
- # xtdb (3)
@phil is that exception coming after the exception handler? if that is, then some of your exception data contains non-edenizable things in the ex-data
you are exposing. You could walk the data and stringify… but easy way to see the data after that middleware is to turn on middleware debug logging: https://cljdoc.org/d/metosin/reitit/0.3.7/doc/ring/default-middleware#inspecting-middleware-chain
@josesanch there is a ring middleware for it, but with reitit, the coercion takes care of keywordizing all parameter types: for example in the reqyest, :query-params
have string keys, but after coercion, the coerced parameters are under [:parameters :query]
with keys keywordized.
here are the parameter types & info how the keys are keywordized in coercion: https://github.com/metosin/reitit/blob/master/modules/reitit-core/src/reitit/coercion.cljc#L35-L42