This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-01
Channels
- # aleph (1)
- # bangalore-clj (5)
- # beginners (24)
- # boot (113)
- # cider (42)
- # cljs-dev (2)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (37)
- # clojure-austin (4)
- # clojure-brasil (3)
- # clojure-france (55)
- # clojure-greece (15)
- # clojure-ireland (4)
- # clojure-italy (13)
- # clojure-russia (37)
- # clojure-spec (50)
- # clojure-uk (31)
- # clojurescript (49)
- # component (12)
- # consulting (1)
- # cursive (6)
- # datascript (9)
- # datomic (27)
- # editors (2)
- # garden (1)
- # hoplon (18)
- # jobs (1)
- # klipse (25)
- # lein-figwheel (1)
- # leiningen (1)
- # luminus (2)
- # om (53)
- # om-next (8)
- # onyx (5)
- # parinfer (4)
- # perun (4)
- # re-frame (13)
- # remote-jobs (1)
- # ring (1)
- # ring-swagger (3)
- # rum (52)
- # spacemacs (36)
- # specter (13)
- # sql (3)
- # untangled (49)
- # vim (11)
- # yada (9)
For anyone else wondering the same question, you can just use a normal handler function to a Bidi route and works like charm.
Yes, you xan
Bidi isn't tied to yada, you can out any Ring compatible thing in there
@kingoftheknoll And you can also mount yada under compojure 🙂
@malcolmsparks got a question about bidi if you don’t mind. Wondering how I can make a rule that will match all routes starting at a base url. I’m going to use aleph to proxy traffic to an old webserver. So like /v2
is the base therefore match all of these /v2/foo/bar
, /v2/very/long/url
. I know that yada has something like this with path-info?
but I’d like to handle this with a plain Aleph handler.
@kingoftheknoll it's something to do with implementing a path matched protocol from bidi. Hopefully matched will turn it up if you grep for it in the yada codebase
honestly it looks like using the bidi catch all would be the cleanest way [true handler-fn]
https://github.com/juxt/bidi/blob/master/src/bidi/ring.clj Resources maybe, just remembered about this example