This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-16
Channels
- # admin-announcements (44)
- # adventofcode (2)
- # avi (1)
- # beginners (22)
- # boot (328)
- # cider (1)
- # cljs-dev (6)
- # cljsrn (29)
- # clojure (164)
- # clojure-chicago (1)
- # clojure-dev (7)
- # clojure-nl (5)
- # clojure-russia (73)
- # clojure-seattle (1)
- # clojure-turkiye (2)
- # clojured (1)
- # clojurescript (98)
- # core-async (6)
- # cursive (26)
- # datomic (9)
- # editors (5)
- # emacs (41)
- # events (3)
- # garden (2)
- # hoplon (125)
- # ldnclj (18)
- # om (178)
- # omnext (8)
- # onyx (5)
- # parinfer (1)
- # proton (5)
- # re-frame (20)
From memory, do this: (reagent.core/flush)
But ... nornally you never need to do that
updates happen via request annimation frames, which is only 16ms away
Are you using reagent 0.5.1 ?
I wonder if, in a round about way, you are asking this question (bear with me if it appears unrelated to start with) https://github.com/Day8/re-frame/wiki/FAQ#5-how-can-i-inspect-app-db
I failed to wire up the reactions in the right way, and so I re-wrote the subscription to have the right reactions… but then things wouldn’t update right
Be sure to read that link above
(Although I acknowledge it is slightly unrelated)
Apart from that (sorry to throw links at you) ... this can help too: https://github.com/Day8/re-frame/wiki/Debugging
basically, I had a subscription, that got something out of the db outside of a reaction, which made it pretty stuck. then I redefined the subscription, and re-rendering everything didn’t fix it
Right, that kind of a messup doesn't happen too often.
Well, it is never a problem for me. But I'm trying to imagine something really complicated and changing, and I'm thinking that might screw things up enough to force a restart
Thinking about it more ... assuming the figwheel reload forces a complete redraw of the components, I'm a bit puzzled about how anything could get messed up.