This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-24
Channels
- # announcements (2)
- # babashka (31)
- # beginners (608)
- # cider (60)
- # clj-kondo (22)
- # cljsrn (28)
- # clojure (14)
- # clojure-europe (5)
- # clojure-nl (3)
- # clojure-spec (1)
- # clojure-uk (19)
- # clojurescript (38)
- # conjure (20)
- # cursive (9)
- # data-science (26)
- # datascript (4)
- # datomic (19)
- # duct (4)
- # emacs (8)
- # figwheel-main (5)
- # fulcro (7)
- # helix (15)
- # leiningen (12)
- # malli (2)
- # off-topic (20)
- # overtone (3)
- # pathom (14)
- # pedestal (10)
- # re-frame (2)
- # reitit (13)
- # ring (13)
- # shadow-cljs (18)
- # spacemacs (8)
Why defnc bean property is not interoperable with helix.dom ? https://gist.github.com/geraldodev/ca7954d3ee9c0e7f98862d7c49ca694c . I was trying to make an Input with some logic so I had to receive props and pass to d/input
@geraldodev I think if you use a symbol, it's assumed to be a JavaScript object, for performance reasons. You'll need to convert it to a js structure yourself using clj->js. I think bean will support that.
@dominicm helix converts it to a Bean. I tried beans ->js with no success. Also tried clj->js after your suggestion. Same result.
Hey everyone, I got an idea in my mind, though I'm not sure I fully understand `core.async` , I was thinking that I could use `channels` as reducers to an `atom` or just a `map` which then could handle multiple requests to change the state more gracefully, does this make any sense? (for some odd reason this channel seems more active than the #clojurescript channel)
@geraldodev your code is slightly incorrect, @dominicm is right that you can’t hand a symbol as props without some additional syntax: https://github.com/Lokeh/helix/blob/master/docs/creating-elements.md#dynamic-props
It would be handy if I could override that if I say "I know what I'm doing", e.g. I have a custom ->js that I know is fast.
it does a check to see if it’s a map and if not, merges it with static props using goog.object/extend
@lilactown every call that does not use literal props needs to to use :&. Is that for performance reason ? because $ needs to compile its arguments to get as much as performance as possible ?