-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(eslint-plugin): add rule no-unsafe-call #1647
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
Thanks for the PR, @bradzacher! 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. |
cbf1242
to
ee060d9
Compare
ecbf587
to
4f10ca3
Compare
47ba6e8
to
296b0e7
Compare
202dca3
to
8fbc865
Compare
0402a87
to
e8d922a
Compare
8fbc865
to
7cd15e7
Compare
Codecov Report
@@ Coverage Diff @@
## master #1647 +/- ##
=======================================
Coverage 95.36% 95.37%
=======================================
Files 147 148 +1
Lines 6904 6916 +12
Branches 1985 1988 +3
=======================================
+ Hits 6584 6596 +12
Misses 112 112
Partials 208 208
|
See #791
I think it's better to introduce these as a number of separate rules.
It makes it easier for people to opt in to the rules, and keeps each implementation small and focused.
This also makes it easier and faster to build and release, as we can build and release smaller rules instead of releasing one monolithic rule.
Based off of #1644
This rule simply checks all call/new expressions, and makes sure that you're not calling/constructing an
any
type.