This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-19
Channels
- # aws (4)
- # aws-lambda (2)
- # beginners (67)
- # boot (38)
- # cider (32)
- # cljs-dev (12)
- # cljsrn (2)
- # clojars (2)
- # clojure (190)
- # clojure-chicago (1)
- # clojure-dusseldorf (2)
- # clojure-germany (1)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-russia (6)
- # clojure-spec (47)
- # clojure-uk (10)
- # clojurescript (59)
- # cursive (9)
- # data-science (14)
- # datomic (24)
- # devops (16)
- # emacs (8)
- # fulcro (25)
- # graphql (30)
- # hoplon (123)
- # juxt (15)
- # lambdaisland (2)
- # leiningen (4)
- # luminus (6)
- # lumo (9)
- # off-topic (11)
- # om (7)
- # onyx (8)
- # re-frame (14)
- # reagent (5)
- # ring-swagger (5)
- # shadow-cljs (46)
- # spacemacs (41)
- # specter (8)
- # testing (8)
- # unrepl (31)
- # yada (18)
@ikitommi Thanks for the suggestiong - I changed the schema to : (s/defschema Messages [s/Str]). I have tried simply outputting a list of strings ("message" "Message2") and it still get { "errors": "(not (sequential? a-java.lang.String))"} response I changed the output then to use json/write-str to output the list and I get the same error. I must be doing something really silly.
@mmer you don’t have to write the output to JSON by hand. Just return the clojure data from the route and it gets encoded based on the client accept headers. e.g. return something like (ok ["kikka" "kukka" "kakka"])
and it should work.