This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-25
Channels
- # admin-announcements (3)
- # beginners (165)
- # boot (123)
- # cider (106)
- # clara (1)
- # cljsrn (20)
- # clojure (199)
- # clojure-canada (2)
- # clojure-dev (3)
- # clojure-poland (29)
- # clojure-russia (7)
- # clojure-taiwan (2)
- # clojurescript (487)
- # cursive (25)
- # datavis (89)
- # datomic (26)
- # gorilla (2)
- # hoplon (15)
- # ldnclj (12)
- # lein-figwheel (9)
- # leiningen (2)
- # liberator (1)
- # off-topic (25)
- # om (380)
- # onyx (26)
- # parinfer (52)
- # portland-or (12)
- # re-frame (28)
- # reagent (132)
guys the debugging stuff is top-notch!
I guess there is nothing I can do, even by debugging, there does not seem to be any issue with re-frame
I am just passing from a two-column to a one-column layout and all the buttons are re-drawn..
but why do they? if the container changes...shouldn't react avoid exactly that? I am still probably looking at some missing reaction
optimization
but now I can debug the events, that's great 😄
@mikethompson: I was trying to update dynamically the children of an h-box
based on a subscription...but the children are props of a h-box
so everything was cascading and re-rendering
I had missed this -> https://github.com/Day8/re-frame/wiki/When-do-components-update%3F
@mikethompson: are we going to see re-frame updated for the reagent 0.6.0-SNAPSHOT?
What is the difference in inlining your children like the following or having the wrapped in a vector?
[v-box
:size "1 1 auto"
:gap "2px"
:children (for [topic (:topics section)]
Let's say I only have children, no other components, are they cached in the same way by React if they are [:div {} here] or [:div {} [here]] ?@gabe: what was the tweak?
@gabe: as far as I know we are on v0.5.0 There's never been a v0.6.0-SNAPSHOT. https://clojars.org/re-frame
@mikethompson: my bad. the snapshot hasn’t been released, but that’s what it’s called in master.
Nothing substantial has been done since v0.5.0. That should be your target
@mikethompson: i think we’re talking past each other. on reagent’s master branch, react dependencies have been updated.
in order to use the newest version of react, changes to reagent were made and those changes will have to be reflected in re-frame.
Oh, sorry, now I see. I misread what you asked.
yeah, we'll wait for a reagent release candidate before we do anything with re-frame
Thanks! We certainly find it nice to use
@richiardiandrea: the reason it works as you have the code is because for
returns a list, which v-box
is happy to accept. When wrapped in a vector, v-box
will consider it to be a single component but Reagent will do the unwrapping (I believe)
I think it is the opposite, lists (and only lists) are squashed inline...by the way in the second case it wants
:key
for each generated child