This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-26
Channels
- # asami (5)
- # babashka (9)
- # beginners (19)
- # calva (14)
- # cider (13)
- # clj-kondo (9)
- # cljfx (2)
- # clojure (51)
- # clojure-bay-area (1)
- # clojure-europe (26)
- # clojurescript (23)
- # code-reviews (7)
- # core-async (1)
- # datahike (4)
- # datalevin (3)
- # emacs (2)
- # kaocha (2)
- # malli (6)
- # nrepl (3)
- # polylith (3)
- # re-frame (15)
- # reveal (1)
- # shadow-cljs (13)
- # tools-deps (6)
@borkdude how would you feel about adding this as a lint? If interested, I could try writing it up
@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 ;).
I'll open an issue with my thoughts and see what I can cobble together in a small pr
I think it makes a good lint, with off being the default - so as not to upset anyone 馃檪
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]}
@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.