This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-13
Channels
- # announcements (13)
- # beginners (52)
- # bitcoin (2)
- # calva (2)
- # cider (7)
- # clara (1)
- # clj-commons (11)
- # clj-kondo (6)
- # cljdoc (14)
- # clojure (68)
- # clojure-belgium (1)
- # clojure-denmark (6)
- # clojure-europe (57)
- # clojure-nl (2)
- # clojure-norway (10)
- # clojure-uk (3)
- # clojurescript (7)
- # code-reviews (17)
- # conjure (1)
- # cursive (5)
- # dev-tooling (11)
- # emacs (9)
- # fulcro (12)
- # hugsql (20)
- # introduce-yourself (6)
- # joyride (2)
- # leiningen (1)
- # lsp (61)
- # malli (30)
- # missionary (11)
- # nbb (6)
- # off-topic (26)
- # portal (5)
- # practicalli (5)
- # re-frame (8)
- # releases (8)
- # sci (21)
- # shadow-cljs (3)
- # sql (17)
- # squint (1)
- # xtdb (3)
I've just started using clojure-lsp
, which uses clj-kondo
for its linting ... and I've noticed it will emit warnings and errors for code inside of comment blocks. Is there any way to disable this globally? I tend to use comment blocks for certain kinds of examples and seeing a bunch of warnings about unused vars is a little distracting.
@U07VBK5CJ I recommend using :config-in-comment
to disable some, but not all linters
example here: https://github.com/nextjournal/clerk/blob/d978d0ca6cb7b10cf1a0c0f370cdba6e096551e3/.clj-kondo/config.edn#L29-L36
Ok, but I am still impressed that the option already exists! I will take a look. Thank you both for the replies !
:config-in-comment {:linters {:unresolved-namespace {:level :off}
:unresolved-symbol {:level :off}
:unresolved-var {:level :off}
:duplicate-require {:level :off}
:unsorted-required-namespaces {:level :off}
:unused-namespace {:level :off}
:unused-binding {:level :off}}}
we use 'rich comments' extensively, this is our kondo config