i think it would be good if we could remove them and have resolvers add components that would stick around in the hierarchy. that way auto components can be stateful.
i think the reason the restriction was in place is so: you add a component from a resolver into a part of hierarchy that was already rendered - obviously the component will not be rendered anymore. but you can have the same problem with onbeforerender() add a component into hierarchy that has already been visibled for onbeforerender() callbacks and now onbeforerender() wont be called on this new component. i think such usecases are rare and its ok to relax the restrictions. -igor On Sat, Mar 5, 2011 at 5:21 AM, Juergen Donnerstag <[email protected]> wrote: > Hi, > > I try to get rid of auto-components. The main reason why we introduced > it was that it should not be allowed to make changes to the hierarchy > during the render phase. I wonder if that assumption is still true. > Any idea? > > -Juergen >
