This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-06
Channels
- # adventofcode (112)
- # announcements (6)
- # beginners (197)
- # boot (3)
- # calva (52)
- # cider (25)
- # clara (14)
- # cljdoc (6)
- # clojure (147)
- # clojure-austin (6)
- # clojure-berlin (7)
- # clojure-brasil (2)
- # clojure-europe (3)
- # clojure-india (4)
- # clojure-italy (8)
- # clojure-new-zealand (2)
- # clojure-nl (7)
- # clojure-russia (7)
- # clojure-spec (29)
- # clojure-uk (63)
- # clojurescript (103)
- # core-async (5)
- # cursive (11)
- # datomic (16)
- # devcards (1)
- # emacs (28)
- # figwheel-main (3)
- # fulcro (97)
- # graphql (4)
- # hyperfiddle (1)
- # jobs (1)
- # kaocha (3)
- # lumo (9)
- # nrepl (4)
- # off-topic (29)
- # onyx (1)
- # pathom (4)
- # pedestal (8)
- # re-frame (24)
- # reagent (1)
- # reitit (13)
- # ring-swagger (7)
- # rum (11)
- # shadow-cljs (79)
- # sql (46)
- # tools-deps (67)
- # yada (8)
@plins haven’t seen examples in the wild, we are using buddy in most projects and wrote an issue to pre-integrate it as a separate module (https://github.com/metosin/reitit/issues/154).
this would be very nice indeed, im quite confused where I should stack it in the middleware list, or how to choose per route which route gets protected with what
yeah. despite the buddy-mw (or any other mw) can be normally, the good practise with reitit is to spec and push the definitions into route data and create a new middleware that reads those at creation time, and configures & mounts the actual mw based on those. Just need to figure out a good new authentication route data spec.
Just need to figure out a good new authentication route data spec
you mean the default endpoints?
somehow those should be put to route-data. “these routes use the basic-auth backend”, “these routes are only for admins and managers”