This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-07
Channels
- # beginners (71)
- # boot (25)
- # cider (204)
- # clara (18)
- # cljs-dev (10)
- # cljsrn (64)
- # clojure (50)
- # clojure-dev (2)
- # clojure-dusseldorf (1)
- # clojure-india (5)
- # clojure-italy (1)
- # clojure-nl (21)
- # clojure-poland (65)
- # clojure-spec (41)
- # clojure-uk (10)
- # clojurescript (4)
- # core-async (5)
- # cursive (2)
- # datomic (17)
- # duct (8)
- # emacs (8)
- # fulcro (1)
- # graphql (21)
- # hoplon (2)
- # javascript (3)
- # lumo (25)
- # mount (5)
- # off-topic (5)
- # onyx (3)
- # portkey (6)
- # re-frame (15)
- # reagent (5)
- # rum (1)
- # shadow-cljs (198)
- # spacemacs (19)
- # specter (2)
👋 Hi everyone! I'm very new to clj(s) (coming from JavaScript) and looking into doing a REST wrap with graphql. I know it will "depend" on my specific circumstance, but I'm considering either A) using js/interop with the latest Apollo-Server (includes support for Schema-stitching, which I might need in the not too distant future) or B) Lacinia+Pedestal. What might be the criteria for choosing between them I should keep in mind?
PS: I'm loving Clojure. Working with it (compared to js and its ecosystem) is the first time I've ever felt I'm in sane company.
after I’ve tagged a map with lacinia.schema/tag-with-type
is there a way to keep the tag if I need to assoc/update/dissoc that map later on in the processing chain?
That's why the docs say "do it last". Also because if it isn't an IMeta, tag-with-type
will return a wrapper object.
but also, for my clients, on every union type I expose a type
field that is a union of all possible types for the union