Fork me on GitHub
#pedestal
<
2018-05-31
>
hagmonk01:05:15

You guys added OpenTracing support! Now I don't have to do it myself! \o/

hagmonk02:05:14

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

martinklepsch15:05:15

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?

ddeaguiar17:05:21

@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.

martinklepsch11:06:07

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 🙂