This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-24
Channels
- # announcements (1)
- # babashka (19)
- # beginners (10)
- # cherry (13)
- # cider (12)
- # clerk (10)
- # clj-kondo (5)
- # clojure (8)
- # clojure-europe (30)
- # clojure-norway (155)
- # clojure-uk (8)
- # clojurescript (27)
- # community-development (2)
- # conjure (8)
- # cursive (26)
- # data-science (7)
- # datalevin (58)
- # datomic (9)
- # deps-new (2)
- # hyperfiddle (19)
- # jobs-discuss (9)
- # missionary (27)
- # nbb (22)
- # off-topic (11)
- # polylith (59)
- # practicalli (10)
- # reitit (6)
- # releases (1)
- # sci (5)
- # scittle (23)
- # xtdb (37)
Is it correct that lint-as
can’t be used to lint several macros using a single custom hook? The documentation for lint-as
uses a phrase “built-in macro” which seems to suggest that custom hooks are excluded.
Is there a way to collect data about how many warnings are related to each macro in the code that clj-kondo doesn’t understand? To the best of my knowledge, most macros confuse clj-kondo but the linting report only contains specific linting issues which aren’t linked to the root problem - an unrecognized macro. Is it possible to link an error or a warning to a specific unrecognized macro (and potentially separate true linting errors and false ones that require unrecognized macros fixes)?
Do you mean that with analysis enabled, it will include the macro name/reference as part of the analysis or that given the data available in the analysis and the source code, it is possible to find the macros?
I gave it a shot but found that it is not always possible to clearly trace each failure to each unrecognized macro.