-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
feat: add auto-accessor fields support to class-methods-use-this #19789
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
Conversation
✅ Deploy Preview for docs-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! Leaving it open for a second review.
Code LGTM. Accessor properties are actually part of the decorators proposal, which is now in stage 3. I'm not sure if it makes sense to call this a TypeScript feature in the docs, especially given that the node type isn't TypeScript-specific (defined in ESTree). While Espree doesn't yet support this syntax (because it's not stage 4) and TypeScript does, that will change soon. Maybe we should call this an "stage 3 syntax" rather than a TypeScript feature? |
@sethamus please double-check your spam folder. I sent you an email earlier this week. 😄 |
@nzakas Yes, sorry, I replied. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks!
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[x] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
Added support for TypeScript auto-accessor fields in the class-methods-use-this rule, aligning with the behavior of @typescript-eslint/class-methods-use-this. The rule now reports an error when an auto-accessor field (declared with the accessor keyword) doesn't use
this
in its initializer function.Is there anything you'd like reviewers to focus on?