Marcelo Nomoto

Yes, I use it to format source files. We even have it running on CI :wink: Using `zprint` was the best way to avoid discussing the way code looks on...

> My question is about how to handle other things after comments. One approach is to simply keep > a comment next to the following line of any sort if...

My latest config was: ```clojure {:binding {:force-nl? true} :fn-force-nl #{:arg1-body :arg1-force-nl :binding :flow :flow-body :force-nl :force-nl-body :noarg1 :noarg1-body} :fn-map {":import" :flow ":require" :flow "comment" :flow "comp" :flow "concat" :flow "def"...

The way I see you understood what I meant. In the clojure community there are lots of patterns that more or less followed. So in my experience having a way...

That was quick! I will take a look on the branch. Thanks!

I'm back to deploying static websites, which means back to confetti :smile: I thought about it from another perspective. If confetti is managing the bucket then adding a force sync...

I'm quite sure that the examples say to use `:body-params` for that after content negotiation. Trying to use body fails because it has an input stream, unless some redirection happens...

This is unrelated to using `api/defroutes`. Calls to `api/annotate` fail because of schema mismatch when running using `s/with-fn-validation`. ```clojure #!/bin/sh #_( DEPS=' {:deps {pedestal-api {:mvn/version "0.3.4"} io.pedestal/pedestal.jetty {:mvn/version "0.5.5"} io.pedestal/pedestal.service...

> Thank you for the suggestion, it makes sense indeed, I think we can rely on the existing rename feature, where the user can just append the new namespace and...

One example (not trivial and only a little tricky): ```clojure ; src/app/a.clj (ns app.a) (defn foo [] :foo) (defn another [] :another) ; src/app/b.clj (ns app.b (:require [app.a :as a]))...