Fork me on GitHub
#clj-kondo
<
2022-02-26
>
Noah Bogart15:02:40

@borkdude how would you feel about adding this as a lint? If interested, I could try writing it up

borkdude15:02:06

@nbtheduke I've been on a team which consistently used keyword style destructuring. I wouldn't want to inflict dozens of new unnecessary lint warnings on them ;).

馃槀 1
imre15:02:05

Off by default?

borkdude15:02:39

We could do that

馃憤 1
Noah Bogart16:02:13

I'll open an issue with my thoughts and see what I can cobble together in a small pr

dharrigan17:02:51

I think it makes a good lint, with off being the default - so as not to upset anyone 馃檪

pfeodrippe00:02:24

I use symbols on my daily job (because it was already like that), but keywords in my personal projects. I didn't want to know it was a workaround, my life is a lie. One reason for keywords is that grep just works, no need to rely on any external tooling, but nowadays the tooling is just there that I don't know if it's a valid reason anymore. Anyway

{:keys [:deal-with-it]}

pithyless18:02:55

@nbtheduke I think it's only fair to also provide an optional linter that does the reverse: catch any :keys that are using symbol bindings instead of keywords. I feel seen by @U02EA2T7FEH - I am one of the dozens.

1