This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-15
Channels
- # adventofcode (121)
- # bangalore-clj (5)
- # beginners (46)
- # boot-dev (9)
- # cider (20)
- # cljs-dev (7)
- # cljsrn (1)
- # clojure (341)
- # clojure-austin (7)
- # clojure-greece (144)
- # clojure-india (3)
- # clojure-italy (5)
- # clojure-spain (1)
- # clojure-spec (34)
- # clojure-sweden (3)
- # clojure-uk (90)
- # clojurescript (24)
- # core-async (1)
- # core-logic (7)
- # cursive (108)
- # datascript (2)
- # datomic (39)
- # events (1)
- # fulcro (225)
- # graphql (8)
- # hoplon (86)
- # instaparse (12)
- # jobs-discuss (2)
- # jvm (4)
- # keechma (1)
- # lein-figwheel (2)
- # leiningen (12)
- # off-topic (26)
- # onyx (35)
- # other-languages (1)
- # pedestal (3)
- # planck (11)
- # re-frame (12)
- # reagent (12)
- # reitit (5)
- # spacemacs (48)
- # specter (29)
- # sql (2)
- # test-check (1)
- # unrepl (71)
@admay I'm prototyping like this:
:fields {:name {:type 'String
:resolve :user/name}
Then I use lacinia.util/attach-resolvers
, and the map with {:user/name #(:user/name %3)}
can be auto-gen based on your schema.hey, I wrote a super fast post on how I’m writing my resolvers at the moment. let me know what you guys think! and please point out typos! I knocked this thing out at the speed of ‘I don’t care how you spell propagate’ https://admay.github.io/graphql-design-evolution/
I would love feedback on the code from step 4 though. I’m looking for more ways to make my services more bullet proof!
Oh, shout out to @guy and @hlship! I gave you a shout out in the article for all the help you guys give around the channel. I hope you don’t mind 😬 I probably should have asked first