This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-31
Channels
- # aleph (12)
- # announcements (4)
- # asami (7)
- # babashka (20)
- # beginners (92)
- # calva (74)
- # clj-kondo (8)
- # cljdoc (70)
- # clojure (47)
- # clojure-dev (29)
- # clojure-europe (27)
- # clojure-nl (7)
- # clojure-norway (3)
- # clojurescript (7)
- # cursive (2)
- # datomic (1)
- # emacs (8)
- # events (5)
- # fulcro (36)
- # gratitude (4)
- # humbleui (25)
- # introduce-yourself (1)
- # lsp (26)
- # malli (6)
- # missionary (8)
- # nbb (50)
- # off-topic (9)
- # pathom (2)
- # pedestal (3)
- # portal (32)
- # practicalli (5)
- # reitit (5)
- # releases (1)
- # ring (6)
- # shadow-cljs (87)
- # sql (31)
- # tools-deps (26)
- # vim (3)
- # xtdb (15)
I'm using clj-kondo with the clj-extras plugin in intellij. Does anyone know if there is a way to suppress the built-in Cursive inspection warnings that are covered by the clj-extras inspection's (absence of) warning? I guess I could just disable all Cursive's inspections, such as "unresolved var", but I worry there may be valid warnings that I would lose that clj-kondo would not warn about.
Through the plugin currently there’s no way to do this automatically. You can pick and choose in the inspection settings to see what fits you workload
Thanks 👍 are those disabled because you think that clj-kondo covers them from your experience?
i guess only "unresolved symbol" is a potential false positive from cursive because it doesn't know about macros via the clj-kondo config. So maybe double reporting a problem isn't much of an issue, or @UQTHDKJ8J do you know if there are other potential false positives from Cursive?