Andrew, yes. >From my understanding, it works like this:
Om renders a tree of nodes. React diffs this tree with the previous version that it rendered to the DOM. Any nodes that existed in the previous version, but not in the current get unmounted. On 22 June 2014 16:40, William Sommers <[email protected]> wrote: > Hey Andrew, > > I put up a small thing to take a look at mounting and unmounting. It is up > here. https://github.com/Will-Sommers/mount-unmount-test > > Your intuition is correct. When a parent component decides not to > previously mounted child component then it is unmounted. I also put up a > small example where a parent component attempts to build a child component > when no data is available to see if will-unmount is called. After looking > at the dom it is obvious that the component is still rendered but without > the data and therefore does not unmount. > > Take a look. > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
