On Mon, Jan 20, 2014 at 2:42 PM, kovas boguta <[email protected]>wrote:
> Sounds like a reasonable solution for now, thanks. > > Is there a reason that the component type should be associated via the > build function, rather than as a protocol method? > The issue is that Om is extremely lazy, we don't even know what we have until we see that we need to update. > If your gonna have a concept of component type, makes more sense to me > to specify that together in the same place with render and all the > lifecycle methods. > This won't help because of what I said above. We could be less lazy of course, but every solution I've considered requires users to return React components directly from their functions instead of delegates. This would encourage users to pass around components instead of functions - I'm not really sure I want to go there. David -- 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.
