You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect the Computed Property list to rerender only the parts that have changed (similar to the controller example), but the entire list is being rerendered. You can verify this by adding some state to the input fields; notice they get cleared in the CP example, but not the controller example.
The text was updated successfully, but these errors were encountered:
So yeah, DS.Model attributes are Computed Properties listening on 'data', and pushing to the store (full or partial) triggers record.notifyPropertyChange('data'); which makes all attribute CPs trigger and in this scenario makes your CP/filterBy based on isActive trigger too.
I'd love to work some more on this and I've got a proof-of-concept working locally with some modifications not suited for production, I need some guidance on how to proceed. cc @igorT@stefanpenner
I'm using
store.update
to update a particular property, but a CP which doesn't rely on that property is being recalculated.I have a jsbin illustrating the problem:
http://emberjs.jsbin.com/loseda/5/edit?html,js,output
I would expect the Computed Property list to rerender only the parts that have changed (similar to the controller example), but the entire list is being rerendered. You can verify this by adding some state to the input fields; notice they get cleared in the CP example, but not the controller example.
The text was updated successfully, but these errors were encountered: