This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-16
Channels
- # announcements (3)
- # babashka (25)
- # beginners (71)
- # calva (18)
- # clj-kondo (52)
- # cljs-dev (94)
- # cljsrn (12)
- # clojure (33)
- # clojure-europe (52)
- # clojure-nl (2)
- # clojure-uk (27)
- # clojurescript (18)
- # clojureverse-ops (4)
- # datomic (64)
- # deps-new (27)
- # depstar (5)
- # events (5)
- # fulcro (5)
- # graalvm (12)
- # graalvm-mobile (82)
- # helix (2)
- # introduce-yourself (1)
- # juxt (5)
- # lsp (10)
- # malli (7)
- # missionary (1)
- # off-topic (41)
- # pathom (69)
- # pedestal (6)
- # re-frame (4)
- # reagent (8)
- # releases (9)
- # remote-jobs (8)
- # shadow-cljs (3)
- # sql (46)
- # tools-deps (44)
- # uncomplicate (1)
- # vim (83)
I am looking for the minimal way to use pedestal table routes on their own (in a datomic http ion as it happens)
at the moment I have
# included io.pedestal/pedestal.route
in deps
# included io.pedestal/pedestal.service
because I want to be able to use io.pedestal.test/response-for
# got a function to create a simple context and call the table-router on it
and now I get a queue of interceptors that the routers has found me:
I guess I then have to call io.pedestal.interceptor.chain/execute
on the interceptors that the router found for me...
which feels like I have crossed a line in reinventing the wheel...
is there a simple way to reuse the table-router,
or should I keep going down this path?
actually maybe that call to execute was the last step I needed
⢠https://github.com/pedestal/pedestal.ions ⢠https://github.com/pedestal/pedestal-ions-sample
is it called 'Pedestal' in reference to the Diana Ross song?
> I'm in the middle of a chain reaction