This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-10
Channels
- # admin-announcements (2)
- # alda (16)
- # beginners (22)
- # boot (55)
- # cider (11)
- # cljs-dev (5)
- # cljsrn (7)
- # clojure (115)
- # clojure-art (1)
- # clojure-finland (3)
- # clojure-greece (18)
- # clojure-madison (2)
- # clojure-norway (2)
- # clojure-poland (50)
- # clojure-russia (122)
- # clojure-uk (9)
- # clojurescript (28)
- # core-async (7)
- # cursive (4)
- # data-science (4)
- # datomic (65)
- # devcards (3)
- # dirac (91)
- # editors (7)
- # emacs (9)
- # hoplon (1)
- # jobs (5)
- # jobs-discuss (10)
- # juxt (2)
- # keechma (7)
- # ldnclj (31)
- # leiningen (3)
- # off-topic (22)
- # om (129)
- # om-next (1)
- # onyx (6)
- # proton (15)
- # protorepl (2)
- # re-frame (49)
- # reagent (13)
- # remote-jobs (1)
- # ring-swagger (2)
- # yada (19)
I use react-selectize and
clojure
(def react-multi-selectize
(r/adapt-react-class (.-MultiSelect js/reactSelectize)))
...
:render [this]
[react-multi-selectize { :onValueChange (fn [] ..... (.setState this #js {"search" ""}) } ]
You can't change a component state from outside of it
(Well, I can’t comment on whether that works with Reagent. But for React, that’s certainly the case.)
ideally you just pass props to a component
Hi everyone. I’ve got a quick interop question. If a regular react component is calling my reagent component, how can I get the props that were passed?
holy crap, it was easier than I thought. It’s just the first argument?! I struggled with this in om.next for 2 days and it only took me 5 minutes with Reagent? I’m in love.