$http.delete shows warning "avoid using JavaScript unary operator as property name" (fix #11090) #11143
Conversation
This file contains hidden or 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
Update error-detector to look for . prefix fix vuejs#11090
painotpi
reviewed
Mar 22, 2020
| @@ -88,4 +88,13 @@ describe('Options template', () => { | |||
| `avoid using JavaScript unary operator as property name: "delete()" in expression @click="delete('Delete')"` | |||
| ).toHaveBeenWarned() | |||
| }) | |||
|
|
|||
| it('warn error in generated function (v-on)', () => { | |||
There was a problem hiding this comment.
The spec name imo should be something like,
"should not warn dot prefixed keywords".
As the warning would appear even on general JS objects with a delete property and not just $http.
13 tasks
flyfishzy
approved these changes
Nov 28, 2020
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.
Update error-detector to look for . prefix
fix #11090
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:
devbranch for v2.x (or to a previous version branch), not themasterbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: