This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-02
Channels
- # aleph (1)
- # architecture (4)
- # beginners (39)
- # boot (12)
- # cider (25)
- # cljs-dev (3)
- # cljsrn (5)
- # clojure (175)
- # clojure-dusseldorf (1)
- # clojure-italy (13)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-spec (52)
- # clojure-uk (110)
- # clojurescript (35)
- # data-science (2)
- # datomic (61)
- # editors (8)
- # emacs (2)
- # fulcro (7)
- # graphql (15)
- # hoplon (1)
- # hyperfiddle (3)
- # jobs (4)
- # jobs-discuss (12)
- # juxt (2)
- # lein-figwheel (6)
- # leiningen (35)
- # off-topic (4)
- # onyx (5)
- # parinfer (1)
- # pedestal (63)
- # re-frame (38)
- # reitit (7)
- # ring-swagger (7)
- # rum (2)
- # shadow-cljs (27)
- # tools-deps (10)
- # uncomplicate (16)
@guy looks like I made a mistake, will recheck my codes. I just realized a point. Thanks
Rechecked, seems like Antlr issue, things are working on my REPL. This problem happens when I try at with Lambda
So... I'm setting up an email verification workflow. I have realised that, outside of setting up another service. I'm not sure how I would go about embedding a confirmation link inside of an email that would point to the graphql
endpoint. Do I need to setup a REST service for this?
In this situation, I would likely create an additional route for the confirmation logic. The GET support is largely there for historical reasons, and it puts the entire GraphQL query in the URL as a query parameter ... big and ugly and not exactly secure.
It looks like you can. https://github.com/walmartlabs/lacinia-pedestal/blob/1305746c750eafdbd2a72a66c85a0a897c76cf22/src/com/walmartlabs/lacinia/pedestal.clj#L547. Is there any documentation around this?
All the service-map
code is trying to split the difference between simple and easy. You can see how straight-forward the code is and just use it, or you can use the individual pieces. That particular line says: if there are routes in the options, just use those (presumably because the calling code started with graphql-routes
but then added more routing).