-
-
Notifications
You must be signed in to change notification settings - Fork 666
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
vue/no-side-effects-in-computed-properties with composition api's computed #1393
Labels
Comments
I think |
sapphi-red
added a commit
to sapphi-red/eslint-plugin-vue
that referenced
this issue
Dec 30, 2020
…mputed-properties refs vuejs#1393
sapphi-red
added a commit
to sapphi-red/eslint-plugin-vue
that referenced
this issue
Jan 3, 2021
…uted-property refs vuejs#1393
sapphi-red
added a commit
to sapphi-red/eslint-plugin-vue
that referenced
this issue
Jan 3, 2021
…s-in-computed-properties close vuejs#1393
sapphi-red
added a commit
to sapphi-red/eslint-plugin-vue
that referenced
this issue
Jan 3, 2021
…s-in-computed-properties close vuejs#1393
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What rule do you want to change?
vue/no-side-effects-in-computed-properties
Does this change cause the rule to produce more or fewer warnings?
more warnings
How will the change be implemented? (New option, new default behavior, etc.)?
new default behavior
Please provide some example code that this change will affect:
What does the rule currently do for this code?
no warning
What will the rule do after it's changed?
show warning like
computed
propertiesAdditional context
Actually, this new feature does not affect computed properties, so it might have to be a new rule.
The text was updated successfully, but these errors were encountered: