-
-
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
Rule Proposal: Validate "emits" section #1787
Comments
Makes sense. I'd suggest |
The first notation (event1(this: undefined)) can be useful to avoid conflict with ESLint core rule object-shorthand. So, I would keep it. |
Makes sense. I think the rule should indeed be called Don't report arrow functions or functions (shorthand or longhand) with an explicit For an autofix, first detect if there is already type information (either only look at the function return type, or detect TypeScript usage in general somehow).
I guess that |
Please describe what the rule should do:
This rule proposal is based on this issue:
vuejs/core#5343
It should ensure that emits section does not break vue component typing.
What category should the rule belong to?
Warns about a potential error (problem)
Provide 2-3 code examples that this rule should warn about:
Valid:
Invalid:
The text was updated successfully, but these errors were encountered: