This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-21
Channels
- # aws (2)
- # aws-lambda (1)
- # beginners (62)
- # cider (31)
- # cljs-dev (16)
- # cljsrn (8)
- # clojure (115)
- # clojure-greece (3)
- # clojure-israel (2)
- # clojure-italy (13)
- # clojure-nl (8)
- # clojure-russia (5)
- # clojure-spec (3)
- # clojure-uk (146)
- # clojurescript (108)
- # clojutre (5)
- # code-reviews (3)
- # cursive (48)
- # datomic (22)
- # editors (20)
- # emacs (7)
- # fulcro (16)
- # graphql (10)
- # mount (2)
- # off-topic (47)
- # onyx (22)
- # re-frame (100)
- # reagent (5)
- # reitit (7)
- # ring-swagger (6)
- # rum (5)
- # shadow-cljs (51)
- # specter (2)
- # tools-deps (95)
- # vim (10)
- # yada (7)
Hey I was wondering if there are any good open source projects built with compojure-api ?? 🙂
New topic. In moving from compojure-api 1.2.0-alpha4 to 2.0.0-alpha20, I've got a broken API. The API :responses schema is (sweet/describe (s/pred bytes?) "Protocol buffer binary encoded data.")
. The HTTP client specifies an accept header of "appplication/msgpack". In my api
options I have specified :format [(m/create (-> m/default-options (msgpack-format/with-msgpack-format)))]
. However the API response is always application/json
and so the clients attempt to unpack the expected msgpack response fails. Do I need to do one of the tricks in the Request and response coercion
section of https://github.com/metosin/compojure-api/wiki/Migration-Guide-to-2.0.0? Or is it something else?
Hmmm, I'm guessing coercion is not the problem here, but I'm still stumped why I can't get "application/msgpack" packed content out of the API.
@dave.tenny some sample code that uses good practices for production 🙂