fix(reactivity): avoid trigger effect in deleteProperty when array length-decrease mutation methods called #6037
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bbcvc
approved these changes
Jun 4, 2022
edison1105
changed the title
fix(reactivity): fix array splice work with JSON.stringify edge case fix(reactivity): fix array length-decrease mutation methods work with JSON.stringify
| @@ -203,7 +203,7 @@ function deleteProperty(target: object, key: string | symbol): boolean { | |||
| const hadKey = hasOwn(target, key) | |||
| const oldValue = (target as any)[key] | |||
| const result = Reflect.deleteProperty(target, key) | |||
| if (result && hadKey) { | |||
| if (result && hadKey && !isArray(target)) { | |||
There was a problem hiding this comment.
Wouldn't this also prevent reactivity from being triggered when using the delete operator with an array?
This seems to work fine on main:
Size ReportBundles
Usages
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fix #6018
the root cause see: #6017 (comment)