This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-07
Channels
- # announcements (1)
- # babashka (79)
- # beginners (177)
- # cider (27)
- # cljdoc (24)
- # cljs-dev (4)
- # clojure (43)
- # clojure-norway (7)
- # clojure-uk (3)
- # clojurescript (52)
- # conjure (12)
- # cryogen (1)
- # cursive (5)
- # data-science (7)
- # datahike (1)
- # datomic (1)
- # dirac (2)
- # helix (14)
- # jobs-discuss (130)
- # juxt (4)
- # liberator (4)
- # malli (2)
- # mxnet (2)
- # news-and-articles (1)
- # nrepl (19)
- # off-topic (27)
- # pathom (3)
- # practicalli (1)
- # re-frame (4)
- # reagent (2)
- # ring (7)
- # shadow-cljs (21)
- # spacemacs (11)
- # vim (38)
- # xml (2)
- # xtdb (17)
@fabrao can you elaborate? I'm currently seeking which one is better for me, helix or reagent, the ability to use hooks is important to me, now reagent has that feature and it got me confused again
oh I didnt say there's an issue. but how can you pass a function as children? I mean, what's the syntax?
Helix is a minimal React wrapper, so it doesn’t try to impose new conventions, just helps you write React in idiomatic Clojurescript.
For render props, just pass a function as a child to your component, as you’d regularly do.
I imagine something like this would work ($ Comp (fn [x] x))
, just make sure Comp
handles the render prop
@eliraz.kedmi Well, in reagent I didn´t know where to put things to be "Reactive". In Helix you use (use-state)
and that´s it. You have to control the updating part with hooks. And besides if you have questions about how it works, you can seek even in React documentation, that have lots of references
the bad thing I don´t like in that is when to use #js
, but I use convertions all the time
to create literal JS objects and arrays
eg: #js {:foo "bar"}
is like {"foo": "bar"}
in JSON