This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-15
Channels
- # adventofcode (6)
- # beginners (63)
- # boot (39)
- # cider (25)
- # clara (9)
- # cljs-dev (27)
- # clojure (100)
- # clojure-dev (39)
- # clojure-dusseldorf (7)
- # clojure-italy (32)
- # clojure-russia (23)
- # clojure-spec (28)
- # clojure-uk (51)
- # clojurescript (197)
- # core-async (44)
- # cursive (3)
- # datomic (14)
- # emacs (4)
- # fulcro (27)
- # graphql (23)
- # hoplon (4)
- # jobs (9)
- # juxt (1)
- # leiningen (3)
- # nyc (1)
- # off-topic (6)
- # om (7)
- # onyx (6)
- # parinfer (11)
- # re-frame (23)
- # reagent (15)
- # ring-swagger (1)
- # rum (15)
- # shadow-cljs (37)
- # sql (24)
- # uncomplicate (4)
- # unrepl (17)
is there an large open source webapp in using rum? I'd like to study how people write larger apps with rum
i have a component that sets the select tag value based on the value of and atom, I'm using rum/react & rum/reactive, but sometimes the element does not update
i remember when working with om that there was some workaround needed to update certain input elements, is that the case with rum as well?
(rum/defc select < rum/reactive [cursor {:keys [options label]}]
[:.form-group
[:label label]
(into [:select.form-control
{:value (or (rum/react cursor) "")
:on-change (fn [dom-event] (reset! cursor (read-string (.. dom-event -target -value))))}]
(for [ [i o] (map vector (range) options)]
[:option {:value (pr-str o)} (name o)]))])
@chrisblom so you are saying that if you log the (read-string...
form you’ll receive events that are sometimes not reflected in the ui?
generally both om and rum have a common problem, which is that because they batch updates, on-change events can get swallowed and cause other kinds of re-renders. supposedly the sablono
library that they both rely upon fixes this problem but maybe you found another issue?
@chrisblom if you have a small repro you should really file a bug. that shouldn’t be required
@chrisblom I've come across this issue too i think. My solution was to not re-render the select, but rely on the native state and kept the changed value in some other atom
I'm getting a no such namespace "prum-preact" when trying to use prum. I've tried adding "prum-preact" to :npm-deps, but I'm not having any luck. Any ideas?
:install-deps too. (I'm using boot-cljs, btw)