i'm not sure if cljfmt can handle this, but i think multi-line assoc calls should have their first key-value pair start on a new line so that all the k-v pairs line up for easy scanning. here, the :join? false is on a different column from all the other pairs, so someone doing a quick scan to see which attributes are set to one could easily miss it.

Yeah, I don't think it can enforce that.

i think i prefer 2-space indentation for function calls when all the arguments are on a new line. i think it better expresses the semantic difference between the function and the arguments it takes. but i'm also ok with leaving it this way if other folks disagree.

This is actually just cljfmt treating lists like other multiline compound data literals. For example:

[:foo
 :bar
 :baz]

I'm not sure if you can tell it to make an exception for lists or if you'd have to make all such data literals indent w/ two spaces on subsequent lines.

Looks like I was wrong and this is specifically configurable in cljfmt: https://github.com/weavejester/cljfmt#formatting-options (see :function-arguments-indentation section). I'm happy to go w/ whatever the team consensus is here.

I like 2-space indentation here as well

Do you all have a preference between the :cursive and :zprint options for that param?

eh. seeing it so strongly rejected in the style guide (from the link in the description of the "community" default option) is making me rethink my stance on this. perhaps we shouldn't go against the default.

i think this is an even better example of why 2 space indentation for function calls is more legible.

Stuart Sierra notwithstanding, I prefer the first ns require to be on the same line as the :require keyword. I think the extra indentation that gives helps break up the require blocks vs imports, uses, and refer-clojures.

I tend to agree, but I think this is another thing that cljfmt cannot (yet?) enforce.