On Wednesday, July 1, 2015 at 12:57:01 PM UTC+1, Dan Kersten wrote: > > Regarding the "Whats next" in the README: > > *looking into swagger integration. I could swear I found some bidi-swagger > bindings somewhere a while back, but am not finding them at the moment* > > Could you perhaps be thinking of the Yada swagger integration? > http://yada.juxt.pro/user-guide.html#Swagger yada.swagger is designed to > be used with bidi. > > https://github.com/juxt/yada/blob/master/src/yada/swagger.clj >
Maybe so! Will definitely look that over before doing anything else. Appreciate the link! > > > On Wed, 1 Jul 2015 at 10:45 Chris Price <ch...@puppetlabs.com > <javascript:>> wrote: > >> Hiya. >> >> >> We really like the syntax of compojure for defining HTTP routes, but have >> had some trouble with use cases where we'd really like to be able to >> introspect the route tree, and aren't able to do so because the nested >> functions are pretty opaque. >> >> After spending some time trying to workaround that, and giving up, we >> decided to look into bidi, which has been awesome. The data-driven route >> tree is really, really useful. >> >> However, a wholesale port of all of our existing apps directly from >> compojure to bidi seemed daunting. Enter `comidi`: >> >> https://github.com/puppetlabs/comidi >> >> This is a small library that uses bidi to build up route trees, but >> provides a compojure-like syntax for defining the routes, and uses >> compojure's "render" capabilities to support flexible syntax for specifying >> your individual handlers for each route. >> >> We've also got a related project that integrates comidi with our >> Trapperkeeper framework and the dropwizard metrics library, to give you >> middleware that will automatically track request metrics for each route in >> your bidi/comidi route tree. >> >> This is all a work in progress: notably, we had built up some prismatic >> schemas around the route structures, but since the latest release of bidi >> ships with its own schemas, we'll probably try to upgrade to that and >> reconcile the differences soon. >> >> We also have some plans for improving the ability to wrap middleware >> around the route tree at various levels, and to look into some ring-swagger >> integration soon. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> <javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
