This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-02
Channels
- # admin-announcements (1)
- # alda (3)
- # beginners (28)
- # boot (155)
- # braid-chat (8)
- # cider (22)
- # cljs-dev (46)
- # cljsrn (24)
- # clojure (94)
- # clojure-belgium (23)
- # clojure-czech (2)
- # clojure-germany (7)
- # clojure-greece (12)
- # clojure-india (1)
- # clojure-japan (1)
- # clojure-russia (118)
- # clojure-spain (18)
- # clojure-spec (40)
- # clojure-sweden (19)
- # clojure-taiwan (4)
- # clojure-uk (5)
- # clojurescript (185)
- # clojutre (10)
- # community-development (5)
- # core-logic (11)
- # css (5)
- # cursive (7)
- # datomic (5)
- # dirac (6)
- # emacs (2)
- # euroclojure (1)
- # events (5)
- # hoplon (355)
- # instaparse (3)
- # jobs-rus (5)
- # lein-figwheel (2)
- # leiningen (5)
- # mount (11)
- # off-topic (8)
- # om (20)
- # onyx (10)
- # other-languages (87)
- # perun (9)
- # proton (1)
- # re-frame (21)
- # reagent (16)
- # specter (28)
- # tmp-json-parsing (5)
- # untangled (19)
- # yada (43)
@therabidbanana: OK, pushed an updated to 0.4.11-SNAPSHOT that removes the need for many forced re-renders. It still does them on post-mutations.
Had to do some refactoring to make the global network activity marker support continue to work. It does possibly require you to change uses of load-data
. There is a new named parameter :reads [:x :y]
that adds the given keys to Om follow-on reads for re-render
post mutations on load-data still trigger a root re-render, but I can probably leverage the :reads
extension to eliminate that as well.
The need for :reads
is a potentially BREAKING CHANGE for apps, since they cannot rely on a complete re-render after load.
Interesting - I'll give it a look.
Another note to the channel in general: I've discovered an error in design around lazily-loaded
. The cookbook recipe on this is wrong as well (though it works).
@tony.kay: did you ever find the bug we were running up against yesterday?
we need to compare app state...I'm guessing they're not identical, and that the new merge function is to blame
I’ve got my head pretty deep in other issues right now, but I’ll get to it soon as I can