This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-02
Channels
- # announcements (1)
- # beginners (119)
- # calva (2)
- # cider (40)
- # cljsrn (14)
- # clojure (145)
- # clojure-dev (122)
- # clojure-europe (4)
- # clojure-italy (9)
- # clojure-nl (5)
- # clojure-spec (2)
- # clojure-uk (32)
- # clojuredesign-podcast (1)
- # clojurescript (10)
- # cursive (44)
- # data-science (1)
- # datomic (53)
- # defnpodcast (6)
- # emacs (6)
- # fulcro (13)
- # garden (25)
- # graalvm (3)
- # graphql (7)
- # jobs (3)
- # liberator (4)
- # nrepl (1)
- # off-topic (21)
- # quil (27)
- # reagent (4)
- # reitit (2)
- # remote-jobs (1)
- # ring-swagger (3)
- # shadow-cljs (3)
- # spacemacs (24)
- # sql (29)
- # tools-deps (68)
- # xtdb (2)
on the front-end-side, what libs are you using for graphql?
I switched from venia to https://github.com/r0man/grafeo. Venia was missing list of object support, probably will be added in future but I've come to appreciate the more concise DSL
I’m using a private fork of district0x’s graphql-query, itself a fork of venia
@donaldball how does it work?
I’m so sorry, I missed this. I’m sure you’ve found the originals by now, but fwiw: it represents graphql queries as clojure data structures. We like it because the queries are manipulable in our editors and in code, and the transformation to graphql is sufficiently straightforward that there isn’t a big cognitive penalty.