V2: Model events during "remove" do not trigger on Col #3806
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE, BREAKING CHANGE This is for the next major, v2.
On the heels of #3803, this prevents events triggered on the model during the "remove" event listener from bubbling up to the collection.
Why? Because the model is "removed" from the collection. You can't
#get
it any more, there're no more references. The collection shouldn't know anything about the model once that event is fired.