This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-09
Channels
- # bangalore-clj (1)
- # beginners (158)
- # boot (8)
- # cider (9)
- # cljsjs (9)
- # clojure (169)
- # clojure-austin (1)
- # clojure-denmark (1)
- # clojure-dusseldorf (5)
- # clojure-italy (9)
- # clojure-losangeles (2)
- # clojure-russia (31)
- # clojure-spec (53)
- # clojure-turkiye (1)
- # clojure-uk (56)
- # clojurescript (145)
- # cursive (72)
- # datascript (4)
- # datomic (3)
- # duct (121)
- # events (9)
- # figwheel (1)
- # fulcro (46)
- # graphql (4)
- # hoplon (16)
- # jobs (1)
- # jobs-discuss (4)
- # leiningen (16)
- # lumo (5)
- # off-topic (38)
- # om (1)
- # om-next (5)
- # onyx (104)
- # parinfer (5)
- # re-frame (106)
- # reagent (1)
- # ring-swagger (3)
- # rum (1)
- # shadow-cljs (235)
- # slack-help (4)
- # unrepl (25)
- # yada (9)
there is no bidi channel but i figured you yada experts might know: is there a way possible to enumerate all paths, given a bidi route definition?
Yes. bidi.bidi/route-seq
I know it is a problem on the client, but the workaround for React Native on Android especially with expo.js is kind of involved
@stijn if your goal is to make a call like curl -X GET --header 'Accept: application/json; charset=utf-8' '
work, and you are able to currently have one like curl -X GET --header 'Accept: application/json' '
work successfully, you can just add "application/json; charset=utf-8"
to the :produces
set of your resource
there might be a better way to do it...but that definitely works for me, at least
(and still has the result return JSON, encoded in utf-8)