I recently submitted a bunch of false positives, where DS complains about missing docstrings for classes and methods that start with a leading underscore. From my understanding of the Google Style Guide for python, they are not externally visible and don’t need a docstring.
Now, I could understand if DS decides to continue to mark those missing docstrings. However, it would be neat if I could ignore only the warnings about missing docs for classes/methods with leading underscore. IISC I can currently only ignore everything or nothing. So my suggestion would be to split up the error codes for missing class/method docstrings into 2 error codes.
DeepSource also reports documentation coverage metrics to let users know about their test and application documentation coverage.
Splitting the issue would fix the problem you’ve mentioned here, but then, the Documentation Coverage metrics would become wrong when the issue is ignored (this is because the doc-coverage metric is not coupled with the issues).
We are currently working on an approach to taking care of this and we hope to get this fixed within the next 24 hours.
Hi, thank a lot! You’re quick It seems to work well on functions with a leading underscore, but I still get a hit for a nonplubic class. Also there are some hits for nested functions (e.g. here), which are also not public.
Haven’t had a too close look on the coverage metrics, yet, tbh.
