-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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(pylint): Reenable too-few-public-methods check #16264
chore(pylint): Reenable too-few-public-methods check #16264
Conversation
Codecov Report
@@ Coverage Diff @@
## master #16264 +/- ##
=======================================
Coverage 76.47% 76.48%
=======================================
Files 997 997
Lines 53245 53238 -7
Branches 6777 6774 -3
=======================================
- Hits 40720 40718 -2
+ Misses 12295 12290 -5
Partials 230 230
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
This rule would be great if it didn't trigger when the class name ends in Mixin
or similar. I'm not sure of the need for re-enabling this rule - any particular reason we'd want this other than going with defaults?
@villebro I agree that there are cases where we want to disable this, but again it's there to help ensure people aren't using a class as a container when a |
@john-bodley ok fair enough 👍 |
Co-authored-by: John Bodley <[email protected]>
Co-authored-by: John Bodley <[email protected]>
SUMMARY
Re-enabling the Pylint
too-few-public-methods
check.TESTING INSTRUCTIONS
CI.
ADDITIONAL INFORMATION