This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-18
Channels
- # adventofcode (9)
- # alda (2)
- # babashka (89)
- # beginners (86)
- # bristol-clojurians (1)
- # calva (54)
- # chestnut (2)
- # cider (18)
- # clj-kondo (19)
- # clojure (160)
- # clojure-brasil (2)
- # clojure-europe (6)
- # clojure-italy (8)
- # clojure-nl (46)
- # clojure-spec (52)
- # clojure-uk (45)
- # clojured (4)
- # clojuredesign-podcast (11)
- # clojurescript (15)
- # core-async (50)
- # datomic (41)
- # devops (3)
- # emacs (10)
- # fulcro (95)
- # graalvm (11)
- # graphql (3)
- # kaocha (1)
- # luminus (1)
- # malli (4)
- # off-topic (13)
- # overtone (3)
- # pathom (8)
- # re-frame (13)
- # reitit (10)
- # shadow-cljs (83)
- # spacemacs (2)
- # specter (9)
- # tools-deps (3)
- # vim (2)
@drewverlee my understanding is that Cursive (IntelliJ) has been following the same formatting rules as the default CIDER ones. I would have thought a style formatter step in the CI would actually be more effective that trying to keep a range of editors in sync. Or you could have a pre-commit hook locally to format the code. There was a brief discussion at https://clojureverse.org/t/autoformatting-clojure-code/1243 There are some other suggestions here: https://blog.ona.io/general/2016/02/07/automating-style-in-clojure.html
thats a very useful insight. Thanks.