@snoe, I could not find a way to implement the support for my custom macro, could you help me, please?
it is confusing, alternatively it seems like kondo is rolling out support for custom macros, it might be time to switch to just use kondo's diagnostics.
yeah, this could be a really nice integration
This is the macro: https://github.com/nubank/state-flow/blob/5919a165ea568b9278dffeb73b44dc82c0dd7f3c/src/state_flow/cljtest.clj#L18
This is our framework for tests and our company uses this as default now
you can find some examples https://github.com/nubank/state-flow#clojuretest-and-matcher-combinators
It looks like it's going to have to be a code change for something like that... you want each flow to be both treated as potential params if a vector, as well as being treated as bound-elements
yes, I think something with a :repeat true
for bound-elements
could help, right?
right, but maybe a match type like bound-params
or bound-element
... I wonder if [:declaration {:element :element :pred :map} {:element [{:element :bound-params :pred :vector} {:element :bound-element :pred :not-vector}] :repeat true}]
would work. So bound-params
would need to be added that brings the reduced bound-scope
in like bound-element
does. Then add the not-vector
pred.
oh, I could test it if you want
well it's got those couple missing pieces but if you add them, it could be a good pr. I probably won't work on it myself, since my feelings with "weird" uncommon macros is that if someone wants support they'll need to add it.
goit it, I still feel confuse about clojure-lsp
's parser, but I can try 🙂
thank you!