is there a configuration to prevent clj-kondo to trigger the unresolved symbol warning on logical variables (ie. symbols that start with ? , used in some dsls like #meander)?

Right now no, but this is something I would consider, e.g. exclude by regex

is my best bet for now to turn off the whole unresolved symbol category?

Please file an issue with a good explanation and examples. @dpsutton I saw a couple of these variables in Metabase's code-base too, right?

@meditans Oh god, no, you can disable it for only some calls, like :exclude [(meander.epsilon/match)]

i think that's unrelated. we have lots of $id type variables which are a dsl macro to pull from databases at test run time

yes, but the relation would be that those variables are sometimes also unresolved, if you don't have special hooks for those macros - maybe I'm wrong

yes good point. they are unresolved and symbols that get meaning from the macro itself and not a previous definition

right, so a regex exclusion would also work for that

the relevant issue https://github.com/clj-kondo/clj-kondo/issues/1647