This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-04
Channels
- # arachne (2)
- # bangalore-clj (3)
- # beginners (34)
- # boot (22)
- # cider (1)
- # cljs-dev (86)
- # cljsjs (3)
- # clojure (42)
- # clojure-argentina (6)
- # clojure-austin (10)
- # clojure-chicago (1)
- # clojure-france (3)
- # clojure-russia (135)
- # clojure-spain (1)
- # clojure-uk (4)
- # clojurescript (69)
- # core-async (13)
- # cursive (11)
- # datascript (6)
- # datomic (8)
- # dirac (2)
- # emacs (10)
- # euroclojure (1)
- # events (1)
- # gsoc (13)
- # jobs-rus (9)
- # lumo (7)
- # off-topic (18)
- # om (16)
- # perun (3)
- # planck (1)
- # portland-or (1)
- # re-frame (25)
- # ring (22)
- # spacemacs (1)
- # untangled (14)
@gardnervickers Hm. That will take a lot more thinking that I have the brain power for today 😉 I'd have to go through the usages and/or specs of that function and make sure we're not changing a behavior that is required.
I think there I was trying to use load
when I should have been using load-field
but load
is intended to be a more general-purpose function than load-data
that can cover the case.
If we allow a load by ident with load
(which we do), then it does make sense that the loaded things should re-render
Knowing that, I guess we were actually seeing an issue where a (load <ident> …)
would not queue up the <ident>
for re-render.
It does work on load-data
however, because there we set data-field
which is what pointed me to that cond
.
I can repro tomorrow in a devcard, pretty out of gas for tonight though. Thanks for your help!
@doddenino I think you need version 0.6.1