It's just that my logs are filling up with warnings. :) Is there a reason that update can't happen during the tree-shaking phase? Or can we mark the updated slots as non propagating? I haven't looked at it closely to evaluate it myself yet.
By the way, I just checked in some uri-parameter code and some improvements to the elephant store to support cached slots (a new elephant feature). Let me know if anyone detects problems with these checkins, I had some merge issues which I believed I resolved correctly but it's been awhile since I've done core weblocks development. Thank you, Ian On Dec 23, 2009, at 11:44 AM, Stephen Compall wrote: > On Dec 22, 2009, at 12:25 PM, Ian Eslick wrote: > >> Am I missing something? dataedit-update-operations is getting called in the >> rendering function for gridedit which results in a circularity warning >> during dirty widget rendering. Is gridedit deprecated? I'm surprised >> someone else hasn't run across this. > > No, you're seeing that right. It's okay in gridedit's case because the > updates it's making are idempotent. That's something we can't detect, and > thought it would be better to warn anyway. > > -- > Stephen Compall > > -- > > You received this message because you are subscribed to the Google Groups > "weblocks" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/weblocks?hl=en. > > -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
