This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-09
Channels
- # announcements (3)
- # asami (1)
- # babashka (19)
- # beginners (84)
- # calva (3)
- # cider (5)
- # clj-commons (22)
- # clj-kondo (29)
- # cljdoc (4)
- # cljs-dev (5)
- # clojure (65)
- # clojure-australia (1)
- # clojure-europe (44)
- # clojure-nl (2)
- # clojure-uk (2)
- # clojurescript (18)
- # code-reviews (12)
- # conjure (2)
- # core-async (12)
- # data-science (1)
- # datomic (47)
- # deps-new (1)
- # emacs (2)
- # events (4)
- # fulcro (35)
- # integrant (1)
- # jobs (5)
- # jobs-discuss (10)
- # london-clojurians (1)
- # lsp (13)
- # music (1)
- # nextjournal (1)
- # off-topic (11)
- # parinfer (3)
- # pathom (6)
- # polylith (11)
- # portal (41)
- # re-frame (4)
- # reagent (13)
- # reitit (8)
- # remote-jobs (3)
- # sci (18)
- # shadow-cljs (34)
- # spacemacs (3)
- # tools-build (12)
- # tools-deps (6)
- # vim (2)
- # xtdb (7)
A question related to muuntaja: Do you guys think it's a good idea that by default keys in a JSON string are coerced to keywords?
This is a big case of "it depends". The differentiator for me is whether it's actually mean to be used as a keyword, or it's actually a string in they key position
I'm still dealing with tech debt from all keys as keywords by default, because of the weirdness you get with things like uuid ids getting converted to keywords, suddenly all the logic gets really weird
Yes. So long as the coercion can be switched off, default coercion to keywords fits my default approach
I tend to think that it's a misused of Clojure keywords, as a the keys could be anything, including weird characters (e.g. whitespace) I know that Clojure keywords support whitespace but it's not advised to have werid characters in a keyword. As far as I understand it, Clojure keywords are meant to be used when the set of possible keys is well known in advance.
It seems that the fact that keywords behave as functions in Clojure cause an overuse of keywords