You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This really intrudes with interactive development, especially if we're formatting on save. If I temporarily want to comment out the args to a fn (forget merge and imagine it's anything), standard-clj is going to put the comment after the fn call instead.
If this is what you want to happen here, fair enough. I think it'll be a hassle, though. Perhaps that comes from me being ok with ) on its own line.
Use case
This came straight outta formatting jank's clojure.core. After running fix on it, I've been scanning the diff to see what standard-clj has changed.
The text was updated successfully, but these errors were encountered:
jeaye
changed the title
Unexpected result: Comments ignored within form
Unexpected result: Comments moved outside of form
Feb 1, 2025
Standard Clojure Style will always gather trailing parens to a single line (as recommended by the Clojure Style Guide and enforced by Parinfer). If you want a ; comment line to 'hold' some parens on the next line, place a comma before them to explicitly show that intent.
Input source
Command
Output
Thoughts
This really intrudes with interactive development, especially if we're formatting on save. If I temporarily want to comment out the args to a fn (forget
merge
and imagine it's anything), standard-clj is going to put the comment after the fn call instead.If this is what you want to happen here, fair enough. I think it'll be a hassle, though. Perhaps that comes from me being ok with
)
on its own line.Use case
This came straight outta formatting jank's
clojure.core
. After runningfix
on it, I've been scanning the diff to see what standard-clj has changed.The text was updated successfully, but these errors were encountered: