This repository was archived by the owner on Nov 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 187
Behaviour when using --convention #482
Milestone
Comments
Hey, you're feedback on this will be much appreciated! |
@saroad2 I am starting work on pydocstyle 6.0 which will elevate conventions to be a first class concept in the checker. I'd be more than happy to have other contributors working on this. I will be targetting the end of this year for the release. Things to do are -
We have a chat at https://gitter.im/PyCQA/pydocstyle# if you want drop by and discuss this. |
4 tasks
Anyone currently working on support for sphinx style docstrings? I'd be happy to take a look if nobody else is. |
Ah, just noticed #595. Good stuff. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a followup issue for #478.
The question here is how the --convention flag affects the chosen rules to be executed when evaluating doctsring. Here is my suggestion:
I think the approach should be that you should split the violations into two categories:
Global - violations which are part of the pycodestyle guidelines
Convention specific - violations that are only relevant for a specific convention.
A definition of a convention-specific violation should look like:
The global rule will be set by default with
convention=None
.Rules that are convention-specific will run only if --convention has been raised with their convention. Global rules will always run. In that way we can prevent false-positive for convention-specific violations
One can choose to add/ignore a violation regardless of the chosen conversion by using --add-select or --add-ignore.
What do you think?
The text was updated successfully, but these errors were encountered: