Hi Chris, Yes it works like you did but on a strict point of view, its better to notify the component its modelobject changed (and the page is also aware that a child component model has changed)... So event if it is not much important yet, it is still better to call #onRemove because it already handles modelChanging/modelChanged, and this could prevent you from having unexpected surprises...
Thanks & best regards, Sebastien. On Sun, Feb 8, 2015 at 8:03 PM, Chris <[email protected]> wrote: > Hi Sebastian, > > currently, I am deleting the element that should be removed from the list > and render the view again. > I am not calling #onRemove, but the code works, too. Therefore, I wanted > to ask you if it is better to call #onRemove. > > br, Chris > >
