This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-31
Channels
- # adventofcode (4)
- # ai (1)
- # announcements (13)
- # babashka (1)
- # beginners (42)
- # calva (15)
- # chlorine-clover (28)
- # cider (7)
- # cljsrn (1)
- # clojure (3)
- # clojure-china (1)
- # clojure-dev (4)
- # clojure-europe (7)
- # clojure-losangeles (1)
- # clojure-nl (3)
- # clojure-nlp (2)
- # clojure-sweden (12)
- # clojure-uk (2)
- # clojurescript (30)
- # code-reviews (36)
- # core-async (5)
- # cursive (10)
- # data-science (1)
- # datalevin (1)
- # fulcro (11)
- # introduce-yourself (1)
- # lsp (10)
- # malli (7)
- # minecraft (24)
- # missionary (10)
- # monads (6)
- # nrepl (4)
- # off-topic (11)
- # portal (4)
- # rdf (1)
- # reagent (3)
- # releases (4)
- # shadow-cljs (4)
- # spacemacs (4)
If I want to configure the clojure-lsp
format rules do I follow the instructions detailed in the cljfmt
repo?
It's just a minor thing but I like to have a trailing comma at the end of my rich comments
like:
(comment
(foo)
,)
and the formatter deletes that last line.Yes, if that is possible with cljfmt it should be able to configure under the :cljfmt setting
Awesome, I just found that page actually. I'm going to make it global once I figure out how. Haha
I use a snippet to create a rich comment blovk that includes a #_()
(I assume for the same reason as using ,
) before the closing paren to prevent cljfmt from moving the closing paren.
If there is a way to configure cljfmt to not move the closing paren, I would be very interested to know.