This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-17
Channels
- # adventofcode (2)
- # beginners (153)
- # cider (14)
- # clara (9)
- # cljs-dev (8)
- # cljsjs (1)
- # cljsrn (4)
- # clojure (124)
- # clojure-dev (9)
- # clojure-france (18)
- # clojure-greece (22)
- # clojure-italy (11)
- # clojure-nlp (5)
- # clojure-russia (9)
- # clojure-spec (21)
- # clojure-uk (40)
- # clojurescript (82)
- # core-async (12)
- # cursive (3)
- # data-science (2)
- # datomic (225)
- # devcards (8)
- # docs (2)
- # duct (1)
- # emacs (18)
- # figwheel (2)
- # fulcro (117)
- # graphql (13)
- # hoplon (10)
- # jobs (7)
- # jobs-discuss (7)
- # keechma (8)
- # leiningen (4)
- # off-topic (16)
- # om (2)
- # om-next (3)
- # perun (11)
- # precept (4)
- # re-frame (24)
- # reagent (2)
- # remote-jobs (8)
- # ring (2)
- # ring-swagger (9)
- # rum (42)
- # shadow-cljs (8)
- # spacemacs (3)
- # specter (7)
- # uncomplicate (10)
- # unrepl (58)
- # yada (9)
@hlship I built a GraphQL service based almost entirely off of the tutorial from the readthedocs pages and am looking to adjust the default URLs for the graphql and graphiql end points. What can I do to see the end points as they are now to adjust them?
@hlship have you considered manually asserting the schema spec when compiling instead of globally toggling on assertion check and then instrumenting compile?
Any particular reason why :my-resolver
in :resolve [:my-resolver "foo"]
needs to be a simple keyword and not a namespaced one? Not a huge deal, but I was surprised to get a spec error when I tried [:my-ns/my-resolver "foo]
Cool, shall I file an issue?
Hmm, actually now that I'm writing test code to reproduce it I can't, probably something else wrong on my end. I'll poke at it more