On Mon, Jan 20, 2014 at 1:58 PM, David Nolen <[email protected]> wrote:
> The issue is that Om is extremely lazy, we don't even know what we have > until we see that we need to update. I don't understand the issue here, unless its a quirk of React. If React is rendering the component, that means shouldComponentUpdate has returned true and we have a concrete component in-hand, no? Is the problem that it checks the component type before asking shouldComponentUpdate? -- 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.
