This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-02
Channels
- # announcements (1)
- # babashka (4)
- # beginners (39)
- # calva (36)
- # cherry (11)
- # cider (23)
- # clj-on-windows (3)
- # clojure (105)
- # clojure-brasil (1)
- # clojure-chicago (3)
- # clojure-conj (8)
- # clojure-denver (4)
- # clojure-europe (18)
- # clojure-germany (5)
- # clojure-hungary (13)
- # clojure-nl (1)
- # clojure-norway (31)
- # clojure-sweden (9)
- # clojure-uk (2)
- # clojurescript (22)
- # core-async (4)
- # cursive (8)
- # data-science (25)
- # datomic (14)
- # devops (1)
- # emacs (9)
- # events (5)
- # holy-lambda (32)
- # hyperfiddle (26)
- # introduce-yourself (2)
- # kaocha (1)
- # leiningen (11)
- # lsp (17)
- # malli (8)
- # off-topic (84)
- # pedestal (4)
- # polylith (2)
- # re-frame (17)
- # reitit (1)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (8)
- # sql (4)
- # tools-deps (8)
- # transit (5)
- # vim (1)
- # vscode (1)
- # xtdb (45)
so https://github.com/metosin/reitit/blob/master/doc/http/pedestal.md deviates from pedestal way of routing? By pedestal way I mean using :server/routes
for routing.
If you read the docs it seems that the routing is processed inwardly from the reitit custom interceptor. And here are more questions.
• What is a better way of using lacinia + pedestal + reitit all at once? https://github.com/walmartlabs/lacinia-pedestal#:~:text=(def%20service%20(lp/default%2Dservice%20hello%2Dschema%20nil)), it suggests using default-service but this creates a pedestal service map (https://github.com/walmartlabs/lacinia-pedestal/blob/88468c0c1ba0bc7a84fcafb20ce6150e48545e18/src/com/walmartlabs/lacinia/pedestal2.clj#L326) which is not compatible with reitit router. Should I just have it defined with a new url with reitit.pedestal
and execute lacinia with lacinia/execute
manually?