-
-
Notifications
You must be signed in to change notification settings - Fork 681
Rule Proposal: use-v-on-exact #271
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
Comments
I like this proposition. Looks like a good |
I like this rule too! I'm thinking it could even go in |
I think all is clear here and ready to be implemented! |
i can make it but i have question: should this work only for build in events or for all? |
armano2
added a commit
to armano2/eslint-plugin-vue
that referenced
this issue
Oct 11, 2018
armano2
added a commit
to armano2/eslint-plugin-vue
that referenced
this issue
Oct 11, 2018
armano2
added a commit
to armano2/eslint-plugin-vue
that referenced
this issue
Oct 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From #269.
Please describe what the rule should do:
In that case, I think that people expected click triggers the
select
and ctrl+click triggers thetoggle
. But actually, theselect
is triggered by the both cases.This rule reports
v-on
directives if multiplev-on
directives exist and those have different system modifiers.What category of rule is this? (place an "X" next to just one item)
[ ] Enforces code style
[X] Warns about a potential error
[X] Suggests an alternate way of doing something
[ ] Other (please specify:)
Provide 2-3 code examples that this rule will warn about:
The text was updated successfully, but these errors were encountered: