fix: fix regressions caused by forEach
to for..of
migration
#884
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.
Context
Handles regressions from migrating from
forEach
tofor..of
loops in #814 (thankfully not in stores yet)Extracted from #882
Changes proposed in this pull request
onRemovedNode
consistent withonAddedNode
; replace somefor..of
with Array filter/mapaddedNodes
in frameManager should've beenremovedNodes
(ref)