Skip to content

Conversation

@visigoth
Copy link

@visigoth visigoth commented Nov 9, 2015

This change triggers a change event for the parent model when the underlying collection changes, since it is akin to the key's contents changing. Views that listen to changes on a particular model don't have to listen to underlying collections as well to know if a model has fundamentally changed.

@visigoth visigoth force-pushed the master branch 2 times, most recently from 3d587a9 to 58a6ca3 Compare November 28, 2015 04:49
externally

This makes sense because a collection changing externally is the
equivalent of a parent set() operation for the collection's key. This
enables scenarios like listening for changes on a parent object and
persisting them without listening for changes to each of the parent
object's relationed collections separately.
@visigoth visigoth force-pushed the master branch 3 times, most recently from 12971f4 to ed3d04c Compare November 29, 2015 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant