-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core): Give warning for set/delete methods on null, undefined, String, Number and Boolean values. Fixes #7381 #7452
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
…ring, Number and Boolean values\nFixes #7381
phanan
reviewed
Mar 8, 2018
try { | ||
setProp(null, 'foo', 1) | ||
} catch (e) {} | ||
expect(`Cannot set reactive property on non-object/array value`).toHaveBeenWarned() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Late to the party, but why use ES6 template literals here (and the next expect()
)?
pkaminski
added a commit
to pkaminski/vue
that referenced
this pull request
Mar 13, 2018
primitive values more precise. Corrects vuejs#7452
This was referenced Mar 14, 2018
This was referenced Mar 19, 2018
f2009
pushed a commit
to f2009/vue
that referenced
this pull request
Jan 25, 2019
f2009
pushed a commit
to f2009/vue
that referenced
this pull request
Jan 25, 2019
…uejs#7818) primitive values more precise. Corrects vuejs#7452
aJean
pushed a commit
to aJean/vue
that referenced
this pull request
Aug 19, 2020
aJean
pushed a commit
to aJean/vue
that referenced
this pull request
Aug 19, 2020
…uejs#7818) primitive values more precise. Corrects vuejs#7452
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.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: