This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-31
Channels
- # aws (2)
- # beginners (101)
- # cider (8)
- # clara (8)
- # cljs-dev (3)
- # cljsrn (17)
- # clojars (2)
- # clojure (67)
- # clojure-austin (2)
- # clojure-finland (1)
- # clojure-france (5)
- # clojure-italy (3)
- # clojure-nl (3)
- # clojure-russia (2)
- # clojure-serbia (1)
- # clojure-spec (72)
- # clojure-uk (112)
- # clojurescript (92)
- # core-async (74)
- # core-typed (2)
- # cursive (8)
- # datomic (2)
- # duct (5)
- # emacs (35)
- # events (11)
- # fulcro (32)
- # instaparse (9)
- # jobs (1)
- # luminus (1)
- # lumo (3)
- # off-topic (118)
- # om (2)
- # onyx (10)
- # pedestal (5)
- # re-frame (21)
- # reagent (48)
- # reitit (40)
- # ring (12)
- # shadow-cljs (113)
- # spacemacs (21)
- # tools-deps (47)
What? You added metrics support in there too? … get out of my head, Charles! I've had half-baked versions of all these things floating around in work repos for a long time now
I’m currently using Yada + Bidi for some project but am considering switching to pedestal for it’s simpler foundations. One reason I haven’t jumped yet is that I’d like to keep the possibility open of using the routes table in cljs. I assume this is not possible with Pedestal right? Is anyone here familiar with workarounds for this?
@martinklepsch, I think opening up cljs usage of routes would require cljs support for interceptors. The later is a high priority and something I’m keen to tackle next. I know you have been involved in the conversations around that issue (https://github.com/pedestal/pedestal/issues/487). I’m sorry it’s taking so long to get to it.
Actually what I’d be most interested in is building route strings from the pedestal routes table. Matching is less important. Looking at the output of expand-routes
this should be possible one way or the other 🙂