This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-14
Channels
- # adventofcode (42)
- # babashka (37)
- # beginners (62)
- # cider (13)
- # clj-kondo (12)
- # cljdoc (1)
- # clojure (80)
- # clojure-australia (2)
- # clojure-dev (43)
- # clojure-europe (69)
- # clojure-italy (8)
- # clojure-nl (10)
- # clojure-switzerland (130)
- # clojure-uk (12)
- # clojurescript (23)
- # code-reviews (8)
- # cryogen (5)
- # cursive (6)
- # datomic (3)
- # duct (4)
- # emacs (12)
- # fulcro (60)
- # kaocha (7)
- # lambdaisland (4)
- # malli (4)
- # meander (1)
- # nrepl (31)
- # off-topic (2)
- # re-frame (16)
- # rewrite-clj (5)
- # shadow-cljs (11)
- # spacemacs (7)
- # xtdb (1)
it seems like concatted-array
could just be mapcat vs. map
Thx @noisesmith, I'll try mapcat.
Thanks again @noisesmith, great advice!
I just got rid off the concatened-array
function, perfect.
We are now entering nitpick territory (this is very nice), but you could use destructuring in your parse-array function arg list to get rid of the first
and rest
calls and also have clearer naming inside the function
Hi @U0J30HBRS! I like to go to niptick territory and I love the destructuring power, so thank you very much for this advice. 🙂 Very elegant now, perfect!
This is a nitpick as well, but I like to keep keys are strings when I get them from somewhere else. You could (group-by #(get % "id"))
and avoid the keyword-isation...