-
Notifications
You must be signed in to change notification settings - Fork 189
Change appropriate "Nested" definitions into "Inaccessible", and add new codes #561
base: master
Are you sure you want to change the base?
Conversation
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.
I couldn't find a good term after scouring python.org for what this might be called. I wanted to avoid "nested" because that exists for classes. "Inner" also didn't feel correct because methods are inside classes. I landed on "inaccessible" because the caller can't access them.
@@ -183,6 +183,7 @@ class ConfigurationParser: | |||
) | |||
BASE_ERROR_SELECTION_OPTIONS = ('ignore', 'select', 'convention') | |||
|
|||
DEFAULT_IGNORE = {"D121", "D123"} |
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.
Other tools have this kind of "we have the ability to report these codes, but their off by default" functionality. I figured this belonged to that category. Note if people are selecting ignore
s today, this will no longer be the default.
@samj1912 this should be ready to review 😄 |
@samj1912 got time for a quick review? |
Some devs want to be able to ignore inaccessible definitions, and some might want to not. This should allow them the option to choose.
(This also helps keep the definition of
is_public
pure and straightforward and correct according to the documentation)Please make sure to check for the following items: