-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add docstrings to classes and functions for automated documentation + Clarity #49
Comments
Good idea - I think Zoltan was doing this for BioCRNpyler. If you can set this up and teach it to me, I can add doc-strings to all of bioscrape cython code (I'm guessing I'm the only person who knows it well enough to do that at this point). Ideally there is a way to get detailed information on which functions don't have doc-strings, right? |
Yeah, once we setup the automated documentation tool we should be able to see what functions don't have doc strings. For now, we can add docstrings whenever we find that they are missing. |
The answer is flake8!
By default, flake8 checks the PEP8 compliance, but with the docstring extension, it can do more:
A way to automate: you can use a pre-commit hook, which runs after you execute the git commit command on your computer. Here's an example config |
This could be a running issue where every developer can try to add docstrings to existing classes and functions. For new additions to the software, we should check every pull request for docstrings as well.
The text was updated successfully, but these errors were encountered: