This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-30
Channels
- # announcements (2)
- # babashka (3)
- # beginners (31)
- # biff (3)
- # calva (40)
- # chlorine-clover (2)
- # clerk (5)
- # clj-kondo (10)
- # clojure (13)
- # clojure-art (1)
- # clojure-denver (16)
- # clojure-europe (44)
- # clojure-nl (1)
- # clojure-norway (27)
- # clojure-sweden (3)
- # clojure-uk (1)
- # clojurescript (49)
- # clr (6)
- # community-development (2)
- # datalevin (10)
- # datomic (63)
- # events (2)
- # fulcro (9)
- # holy-lambda (15)
- # honeysql (8)
- # hoplon (6)
- # hyperfiddle (9)
- # introduce-yourself (1)
- # kaocha (1)
- # london-clojurians (2)
- # matrix (1)
- # nbb (7)
- # off-topic (38)
- # polylith (6)
- # re-frame (4)
- # reagent (2)
- # releases (3)
- # sci (13)
- # scittle (5)
- # shadow-cljs (6)
- # sql (5)
- # tools-deps (4)
- # vim (33)
- # web-security (8)
- # xtdb (2)
I'm facing a mysterious problem where clj-kondo flags two "error: get-in with single key" in our CI job. However • We haven't enabled the single-key-in linter and it's off by default, right? • There are get-ins with single key all over the file but it only flags two • Running the same clj-kondo script locally passes cleanly Any ideas?
CI is using 2023.07.12 and I'm on 2022.09.08, so that's one difference. Let's try upgrading
oh ok, mystery solved: a colleague had enabled the linter in master and fixed all existing occurrences
and since the CI runs on the merge commit (`/pull/1234/merge`), clj-kondo only saw my new additions