This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-04
Channels
- # aleph (10)
- # announcements (2)
- # babashka (2)
- # beginners (101)
- # calva (17)
- # cider (11)
- # clara (6)
- # clj-kondo (25)
- # cljsrn (33)
- # clojure (181)
- # clojure-dev (15)
- # clojure-europe (3)
- # clojure-italy (4)
- # clojure-nl (8)
- # clojure-uk (22)
- # clojurescript (111)
- # clojutre (58)
- # cursive (31)
- # data-science (1)
- # datomic (10)
- # emacs (6)
- # ethereum (1)
- # fulcro (20)
- # graalvm (3)
- # jackdaw (5)
- # leiningen (5)
- # off-topic (31)
- # re-frame (2)
- # reitit (10)
- # shadow-cljs (9)
- # spacemacs (16)
- # sql (8)
- # tools-deps (16)
- # vim (17)
I have upgraded [com.fasterxml.jackson.core/jackson-databind "2.9.9"]
to 2.10.0 because lein nvd
reported 6 vulnerabilities for 2.9.9
. This then causes jsonista to stop working, and that library is used in a lot of metosin libraries
just a heads up
@roklenarcic could you write an issue out of that into jsonista. PR also welcome, if the fix is simple, thanks
@roklenarcic pushed out [metosin/jsonista "0.2.5"]
, tests pass at least.
the version I used was 0.2.2 because that's what comes with lastest muuntaja
So I guess, there's other projects where to bump version too 🙂
but thanks
Does reitit automatically perform spec coercion on on the values of response object keys, where the key names are the same as clojure spec keywords? For example, if I return a body
containing this object:
{ :user/birthyear "ikitommi" }
and this spec is defined elsewhere:
(s/def :user/birthyear integer?)
will reitit automatically throw an error? It seems to be behaving that way in our system, but I don’t see anything in the reitit docs that suggest that behavior.