This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-17
Channels
- # admin-announcements (4)
- # aws (26)
- # beginners (88)
- # boot (132)
- # cljs-dev (4)
- # cljsrn (35)
- # clojars (11)
- # clojure (41)
- # clojure-art (33)
- # clojure-austin (1)
- # clojure-chicago (4)
- # clojure-dev (3)
- # clojure-russia (2)
- # clojured (3)
- # clojurescript (9)
- # community-development (19)
- # datomic (34)
- # devcards (2)
- # editors-rus (4)
- # hoplon (29)
- # leiningen (4)
- # music (2)
- # off-topic (21)
- # om (69)
- # other-lisps (1)
- # perun (6)
- # re-frame (1)
- # reagent (9)
- # spacemacs (3)
- # yada (13)
Schema checking does not seem to be working for POST requests. Is that only for GETs at the moment?
@joshg: What media-type are you using?
I'll look into it, in 1.1 forms and bodies are treated separately from the other params (body processing is asynchronous and supports streaming)
I could have missed doing something obvious
i'll check basic forms first
RE :raw & :body, perhaps records would fit the bill slightly better there, as it would play into Yada's protocol system very well.
@malcolmsparks: I was using application/json
content type
thanks for the report - the code in yada is incomplete: https://github.com/juxt/yada/blob/master/src/yada/request_body.clj#L117
good excuse to fix this now, for all affected media types. @imre and I were putting in transit last week and we skipped out on the schema coercion side - I'll put some tests in tonight (if not, in the next few days) and fix this
@joshg: should be all fixed now. Thanks for the report. New release is [yada "1.1.0-20160117.205509-8"]
There's no body coercions but I think that if you want to ingest JSON bodies chances are you want yada to leave the alone, it's not quite the same case as query/path params etc.