I really like yada so far

Yada startup isn't very quick is it. I wonder, how do the leiningen folks typically address that for quick development turnaround?

I use Stuart Sierra's reloaded workflow. Typically dev turnaround is subsecond

@malcolmsparks https://github.com/stuartsierra/reloaded?

@matan I use reloaded.repl myself ( https://github.com/weavejester/reloaded.repl ), but there may be another setup in edge ( https://github.com/juxt/edge ). Yes, reloading is pretty quick (in fact one of the reasons I switched from pedestal to yada)

Edge uses weavejester's reloaded.repl

By the way, should I open an issue for these: - https://clojurians.slack.com/archives/C0702A7SB/p1498915768699940 - https://clojurians.slack.com/archives/C0702A7SB/p1498920492028993 or did I miss something?

@nha please do

I am a bit confused by the first one

Yada handlers and Ring handlers are not complimentary

A yada handler is a Ring handler, almost. The only difference is the async response

Do you mean that this should work?

(yada/resource
  {:methods
    {:get
      {:produces …
       :response (fn [ctx] (my-ring-handler ctx))}}})

Not quite. That would render as a map. You would need to merge the ring-handler response with the (:response ctx)

Ah right (don’t have a yada repl handy). That makes sense, so this is probably a non-issue