warn about :click being a possible mistake ( user meant to use @click)

[sktguha]

Please describe what the rule should do:

If the programmer is using :click (instead of @click) to try to capture click event the rule should warn the user that :click will create a data attribute instead of listening in on the event handler , which they probably intended

What category should the rule belong to?

• Enforces code style
• Warns about a potential error
• Suggests an alternate way of doing something
• Other (please specify:)

Provide 2-3 code examples that this rule should warn about:

     <button :click="doSearchAction()">Search</button>

in the example above, it is correct code only, but this will result in an attribute called click created on the button with the value the result of doSearchAction

Additional context

Infact this rule can be extended for any dom events like focus,hover etc

I can start work on this if this is green lighted

[michalsnik]

Hey @sktguha Interesting rule proposition. So you mean to create a rule that would report usage of any binding that happens to be named exactly as possible events on the given element?

[sktguha]

Ya that's what I meant . I mean I used :click on an element and called a function. And I was wondering for sometime why that is not working properly. So I want that others won't make the same mistake.

I suppose that :click is most common . And then others like :blur etc.

"usage of any binding that happens to be named exactly as possible events on the given element?"
Regd the above, i.e making it fully generic, I am not sure fully how to proceed in this case. Although I feel this is the best way, but we do need to consider that the rule doesn't become annoying , where the programmer actually meant to use :event , event may be some little used dom event , so in that case may not be fully applicable.

[michalsnik]

We might allow users to whitelist props, that they are certain about @sktguha

[sktguha]

Ya that could work too.
Hmm ok then let me know what final decision is taken on this and if so how to proceed about it.

[sktguha]

let me know in case of any update @michalsnik

[sktguha]

hello anything @michalsnik ?

[sktguha]

hi, anyone interested in this ? I have often run into this issue so the eslint rule will be a good addition