how does the problem manifest itself when you use the above config?

so I'm defining my weird def to lint as normal def, but since I use my-weird-def with earmuffed name always, so I'm actully defining my-weird-def as def :^dynamic, hope that make sense:slightly_smiling_face:

can you please give an example/repro of what code goes in and what undesired warnings come out?

sure, take this repo for example: https://github.com/teknql/systemic it has {:lint-as {systemic.core/defsys clojure.core/def}} , but from usage example its defsys all have earmuffed name. clj-kondo [earmuffed-var-not-dynamic]: Var has earmuffed name but is not declared dynamic: server

so this case I guess it'd be more proper to lint systemic.core/defsys as def :^dynamic i guess

I can't reproduce:

$ clj-kondo --config '{:lint-as {foo/deffoo clojure.core/def}}' --lint - <<< "(ns foo) (declare deffoo)  (deffoo ^:dynamic *foo* 1)"
linting took 5ms, errors: 0, warnings: 0

or, if don't want to be warned for defining names with earmuffs that are not dynamic, turn off the linter that does that

do you mean that deffoo always creates a dynamic var?

yeah, turing that off is another way 😄

yes, deffoo always creates a dynamic var

@U0599HVJX70

$ clj-kondo --config '{:config-in-call {foo/deffoo {:linters {:earmuffed-var-not-dynamic {:level :off}}}} :lint-as {foo/deffoo clojure.core/def}}' --lint - <<< "(ns foo) (declare deffoo)  (deffoo *foo* 1)"
linting took 58ms, errors: 0, warnings: 0

:config-in-call lets you disable this linter only in calls to your macro, see above

in the example code above it is not the case that defsys creates a dynamic var

you can tell because you can grep the code base for :dynamic and Dynamic

yeah, i know, i happen to like its convention of earmuffed name this case, nothing about dynamic or not this case

thanks @U04V15CAJ, that works!