This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-05
Channels
- # announcements (14)
- # aws (7)
- # babashka (28)
- # beginners (16)
- # calva (2)
- # cider (1)
- # clj-commons (8)
- # clj-kondo (29)
- # clojure (213)
- # clojure-europe (39)
- # clojure-losangeles (2)
- # clojure-norway (9)
- # clojure-spec (2)
- # clojurescript (11)
- # community-development (1)
- # conjure (2)
- # cursive (6)
- # datalevin (2)
- # datomic (8)
- # emacs (29)
- # events (1)
- # fulcro (22)
- # graalvm (14)
- # improve-getting-started (1)
- # jobs (1)
- # lambdaisland (5)
- # leiningen (4)
- # lsp (7)
- # malli (13)
- # meander (11)
- # membrane (13)
- # off-topic (23)
- # polylith (9)
- # re-frame (4)
- # reagent (7)
- # reitit (6)
- # releases (2)
- # sql (58)
- # testing (8)
- # tools-deps (18)
- # web-security (2)
Hi guys! I don’t understand why clj-kondo is disabled here (emacs). I follow the use-package
installation. The flycheck-verify-setup
give me this:
Yeah, strange. I'm not really familiar with use-package, so perhaps try #emacs
What you could also do is manually do (require 'flycheck-clj-kondo)
I'm on schedule for the planned release today: just one more issue... https://github.com/clj-kondo/clj-kondo/projects/1 (see high priority column)
I've got a macro that takes in a list of symbols and returns a do
expression containing a defonce
for each those symbols. This causes red squiggles with an Unresolved symbol
warning for those symbols both inside the call to the macro and everywhere else those symbols are referred to in the file. I can fix the warnings inside the macro call with def-catch-all, but that does nothing for the warnings in the rest of the file. Is there anything I can do to make this work?
Hi! I think you could write a hook for this macro:
https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md
A (hopefully) gentle introduction:
https://github.com/clj-kondo/hooks-workshop-clojured-2022
tl;dr: the :macroexpand
hook allows you to more or less copy your macro to your configuration and is probably the least amount of effort. The :analyze-call
macro allows you to do more and with more accuracy but might be overkill for your macro which just defines vars.
yep, :macroexpand was exactly what I needed, thanks!