This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-04
Channels
- # announcements (7)
- # beginners (37)
- # boot (6)
- # calva (13)
- # cider (13)
- # cljdoc (52)
- # cljs-dev (9)
- # clojure (117)
- # clojure-europe (3)
- # clojure-italy (12)
- # clojure-nl (21)
- # clojure-russia (8)
- # clojure-spec (77)
- # clojure-uk (20)
- # clojurescript (142)
- # community-development (6)
- # cursive (5)
- # datomic (13)
- # emacs (9)
- # figwheel-main (20)
- # fulcro (33)
- # graphql (11)
- # instaparse (6)
- # klipse (1)
- # off-topic (7)
- # om (8)
- # quil (7)
- # re-frame (11)
- # reagent (39)
- # reitit (10)
- # shadow-cljs (36)
- # spacemacs (3)
- # test-check (3)
- # tools-deps (83)
- # utah-clojurians (31)
- # vim (14)
possibly dumb question - if i update a lot of the db in one event, all of the subscriptions should all change value during the same "tick" (so to speak)? There shouldn't be any render moment where the data is updating one-at-a-time?
updates are "framed", so yes they should all happen together.
with the possible caveat that I think it might happen over two or three frames if there are lots of updates.
but then the intermediate value isn't used to update the UI, if I understand correctly.
tl;dr, you should never see "tearing" in the UI.
that's a great way to cause "cannot read property foo of undefined" and so on.
None yet I believe. https://github.com/Day8/re-frame/issues/457
I usually add a comment, but I like oconn’s approach with extracting a function
that's my issue! 😛 still nothing huh...