This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-02
Channels
- # admin-announcements (15)
- # aws (35)
- # beginners (6)
- # boot (183)
- # cider (51)
- # clara (17)
- # cljs-dev (32)
- # clojure (67)
- # clojure-dev (7)
- # clojure-india (1)
- # clojure-japan (3)
- # clojure-norway (1)
- # clojure-russia (26)
- # clojurescript (85)
- # clojurex (4)
- # community-development (1)
- # cursive (18)
- # data-science (1)
- # datomic (46)
- # devcards (29)
- # events (7)
- # funcool (21)
- # hoplon (10)
- # ldnclj (2)
- # lein-figwheel (16)
- # off-topic (60)
- # om (37)
- # onyx (8)
- # re-frame (23)
- # reagent (5)
- # yada (6)
How are people handling load items from server (initial payloads etc..), a global :loading bool in app-db or actually substitute the values e.g. :people { :status :loading } -> :people { :status :ok :value [{p1}.{pe}] } ?/
@nowprovision: if you have N things to be loaded then, one way or another, you'll need N flags to indicate the success or otherwise. You can use the existence of the data itself as the flag of course. :people
is nil if not loaded, or otherwise a value.
Of course, if there are errors, then you may want to keep them too. Which leads you back towards the {:status :ok :values [...] :error "timeout"}
thanks.
thinking out load again, https://github.com/Day8/re-frame/blob/master/examples/todomvc/src/todomvc/views.cljs when using on-click #(dispatch blah) then wouldn't this break = and identical? causing un-necessary computation of the render payload.. However this is mitagated because render will only be called when either the props passed in changes or ratoms deref?
rethinking my design decisions again, here https://github.com/nowprovision/webhookproxyweb/blob/master/src-cljs/webhookproxyweb/components/webhook/view.cljs#L75 I have a free floating atom to work with re-agent forms proj, would it make more sense to use a cursor on the ratom instead https://github.com/reagent-project/reagent/blob/master/src/reagent/ratom.cljs#L240?
when I dispatch an event in a handler is there some guarantee that the app-state has changed (by current handler) when the dispatched event is handled?
@martinklepsch: yes, dispatches get serialized (via core.async channel)
@darwin: thanks
@martinklepsch: btw. the router loop is really simple, it handles a single event at a time, in this loop: https://github.com/Day8/re-frame/blob/master/src/re_frame/router.cljs#L45
yeah I remember seeing this before. The original reasons why I doubted suddenly vanished 😜
guys, if re-com/google closure throws a Uncaught TypeError: Cannot read property 'appendChild' of null, what am I doing wrong?
@richiardiandrea: this might not be related to re-frame or re-com, something just gets evaluated to null and you call .appendChild on it
sanity hints might help here: https://github.com/binaryage/cljs-devtools/releases/tag/v0.4.0
mmm...it does it in crosspagechannel.js:485
parentElm.appendChild(iframeElm);
I don't even know where it comes from, I assumed it was reframe
oh great thanks
ok will investigate, maybe it is not related as you said
@darwin clj-devtools is just so good
@darwin: it was due to the fact that my compiled js was included in <head> and not in <body>
can a :child of a box
be a react component in re-com
?