@borkdude https://github.com/clj-kondo/clj-kondo/issues/1164 is this something that would be useful?
Replied in the issue
me also 🙂
I'll let the issue be open to gather feedback from the community first.
If this doesn't end up in clj-kondo eventually you can write a custom hook to handle cond and condp yourself
how would I go about writing custom hook, we’ve being bitten in our rear end few times over last days because of condp lacking default case
I will write a small one
https://github.com/clj-kondo/clj-kondo/issues/1164#issuecomment-776679048
thank you Michiel
np. you might have to do some more work to take into account :>>
, e.g. filter it out, but if you're not using that this should already be sufficient
Idea for linting: warn about useless ->
in the code like (-> 'x)
.
Sometimes during refactoring I remove all forms in threading macro and miss remaining macro itself.
Maybe also (-> x y)
feel free to post an issue
“Maybe also (-> x y)” NO!
Why? That is like (y x)
with extra chars.
I'm not talking about when y
is a form, that should be fine, but for a symbol or keyword.
Sometime I would like to emphasize that x
is more important in the context than y
. Like (f a (-> b xform))
. This allows me to place accents.
https://clojurians.slack.com/archives/CHY97NXE2/p1612971030126000?thread_ts=1612969334.125300&cid=CHY97NXE2
Interesting, never thought about using it that way. Thanks.