-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(eslint-plugin): use defs, not definitions, in rule schemas #5534
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(eslint-plugin): use defs, not definitions, in rule schemas #5534
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. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Codecov Report
@@ Coverage Diff @@
## main #5534 +/- ##
==========================================
+ Coverage 91.57% 93.92% +2.34%
==========================================
Files 132 290 +158
Lines 1496 10017 +8521
Branches 226 3016 +2790
==========================================
+ Hits 1370 9408 +8038
- Misses 62 330 +268
- Partials 64 279 +215
Flags with carried forward coverage won't be shown. Click here to find out more.
|
That's on production too 😞. |
PR Checklist
Overview
Does a find-and-replace per the issue:
definitions
->$defs
.