This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-28
Channels
- # 100-days-of-code (10)
- # announcements (2)
- # architecture (16)
- # beginners (51)
- # bitcoin (3)
- # calva (1)
- # cider (6)
- # cljdoc (8)
- # cljs-dev (14)
- # cljsrn (4)
- # clojure (59)
- # clojure-italy (26)
- # clojure-losangeles (1)
- # clojure-nl (13)
- # clojure-spec (54)
- # clojure-uk (81)
- # clojurebridge (4)
- # clojurescript (20)
- # core-async (16)
- # cursive (39)
- # datomic (27)
- # emacs (12)
- # events (1)
- # figwheel-main (20)
- # fulcro (35)
- # funcool (1)
- # graphql (9)
- # hyperfiddle (10)
- # jobs (1)
- # jobs-discuss (7)
- # keechma (10)
- # lumo (22)
- # nrepl (18)
- # off-topic (28)
- # onyx (3)
- # pedestal (4)
- # re-frame (8)
- # reagent (8)
- # ring (4)
- # rum (3)
- # shadow-cljs (29)
- # testing (5)
are there any diagrams or docs for the interceptor flow that lacinia-pedestal implements outside of the API docs?
I’m having a similar question — I’d like to include lacinia-pedestal’s interceptors as part of another service map and routes. So /graphql
, /graphql-ws
and /_graphiql
would be just 3 routes inside a much larger route specification. I’d also like to add my own interceptors (e.g. authentication, rate limiting and so on) in front of them. What is the recommended way to do that?
I guess I could start with http://walmartlabs.github.io/lacinia-pedestal/com.walmartlabs.lacinia.pedestal.html#var-default-interceptors and go from there?
I haven't gotten to actually reading the code but I think that's what I'm going to have to do
I was thinking of adding a transformation stage, so that a resolver could return a query and then it's children could manipulate the query, before doing the actual GraphQL JSON stage
It's grown a bit haphazardly from specific code needed to setup for our own servers, to something more general that can be used a bit piecemeal to setup something else. So there's the simple route, just use service-map
or the intermediate approach (pass some options to service-map
) or the heavy approach: reuse bits and pieces of code called from service-map
.