-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: use no-restricted-syntax to enforce created options in rules #6074
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
chore: use no-restricted-syntax to enforce created options in rules #6074
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
ac0ee9f
to
ee43230
Compare
man GH did something fucky there. The PR targetted the branch in #6073. When I closed the PR the branch was deleted so it closed this PR and i had to undelete the branch to be able to change the PR target. that was weird |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Huh, that is weird. It used to retarget the PR nicely :( |
PR Checklist
Overview
Uses
no-restricted-syntax
to enforce always usingcreate
's second parameter, rather thancontext.options
.