This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-04
Channels
- # aleph (1)
- # announcements (7)
- # beginners (22)
- # calva (31)
- # cider (2)
- # clj-commons (1)
- # clj-http (2)
- # clj-kondo (10)
- # cljsrn (33)
- # clojure (18)
- # clojure-europe (7)
- # clojure-nl (3)
- # clojure-uk (2)
- # clojurescript (93)
- # depstar (3)
- # events (1)
- # figwheel-main (3)
- # fulcro (13)
- # graalvm (95)
- # graphql (1)
- # introduce-yourself (1)
- # lsp (92)
- # off-topic (2)
- # pathom (11)
- # releases (1)
- # shadow-cljs (33)
- # specter (6)
- # tools-deps (4)
- # vim (3)
- # web-security (1)
- # xtdb (7)
Hello, any body using lacinia successfully transitioned to apollo graphql federation as described here https://lacinia.readthedocs.io/en/latest/federation/implementation.html? My current code looks like this
(-> graphql-schema-edn-file
io/resource
slurp
edn/read-string
(attach-scalar-transformers transformers)
(attach-resolvers resolvers)
(schema/compile {:promote-nils-to-empty-list? true}))
Are there any helper functions that allow me keep my edn schema file?
If I convert my edn schema file to a raw graphql sdl file, can I still use the attach-*
helpers?
ā¦ ultimately can anyone who is using graphql federation on a big project share how the equivalent block of code above looks for them š