This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-16
Channels
- # announcements (8)
- # aws (28)
- # babashka (26)
- # beginners (125)
- # calva (18)
- # chlorine-clover (2)
- # cider (12)
- # cljs-dev (6)
- # cljsrn (4)
- # clojure (134)
- # clojure-europe (31)
- # clojure-italy (2)
- # clojure-nl (14)
- # clojure-uk (83)
- # clojurescript (81)
- # conjure (4)
- # cursive (2)
- # datomic (145)
- # emacs (13)
- # events (3)
- # figwheel-main (14)
- # fulcro (30)
- # graalvm (23)
- # graphql (15)
- # helix (21)
- # jackdaw (20)
- # juxt (1)
- # lambdaisland (4)
- # leiningen (2)
- # malli (12)
- # meander (22)
- # observability (22)
- # off-topic (27)
- # pedestal (3)
- # re-frame (12)
- # reitit (1)
- # releases (2)
- # rewrite-clj (3)
- # shadow-cljs (67)
- # spacemacs (7)
- # sql (1)
- # tools-deps (19)
- # unrepl (2)
- # xtdb (25)
I feel like I asked this before, when I want to pass js object props to a component when using $, how do I do that? Is {:& (theProps)}
my only option? It feels inefficient.
Oh, you actually optimize this case. By checking for (seq m) and just returning it if so, nice.
My colleague has expressed similar wishes though, except that everything was #js by default… I didn't like that as much because mutability.
I did just discover that the appliedscience js-interop library has j/lit for this use-case, but I'm trying to reduce my dependence on that. I think cljs-bean & goog.object are better/good enough, respectively.
i’m not sure how safe that would be tho since there’s a lot of objects out there that you might not want those semantics 😛
@lilactown also, the new proxies feature would be a real thorn in that. Imagine doing a get on an object and it starts doing stuff.
well that’s already possible in CLJS 😛 since get
is just a protocol, anyone can do anything in it!