This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-16
Channels
- # atlanta-clojurians (8)
- # beginners (103)
- # boot (22)
- # boot-dev (1)
- # cider (36)
- # cljs-dev (55)
- # cljsrn (3)
- # clojars (25)
- # clojure (104)
- # clojure-brasil (1)
- # clojure-dusseldorf (2)
- # clojure-italy (8)
- # clojure-norway (9)
- # clojure-russia (15)
- # clojure-spec (6)
- # clojure-uk (26)
- # clojurescript (246)
- # cursive (26)
- # data-science (1)
- # datomic (22)
- # dirac (11)
- # editors (1)
- # emacs (8)
- # fulcro (50)
- # graphql (11)
- # hoplon (1)
- # jobs-discuss (27)
- # leiningen (44)
- # luminus (33)
- # lumo (2)
- # mount (1)
- # off-topic (8)
- # onyx (5)
- # parinfer (4)
- # reagent (94)
- # ring-swagger (14)
- # shadow-cljs (37)
- # spacemacs (10)
- # specter (3)
- # tools-deps (4)
- # unrepl (14)
- # yada (5)
Just learned about relay, and only implemented Lacinia, but from https://facebook.github.io/relay/docs/en/graphql-server-specification.html it seems you have to support id's for everything, and have and explicit ordering/paging. This would be outside of the scope of Lacinia.
I tryied to parse a sample schema.graphql
with lacinia and lacinia cant read the input
statement in mutations
what do you mean by sharing schemas? On the client we use the schema of the backend, which is generated by lacinia.
Has anyone manage to get Lacinia
graphql implementation to work with luminus?
Including getting the Docs
explorer of GraphiQL to work with the query root and schema.
I have got it working with a regular ring server, not Luminus but a similar underlying stack