-
Notifications
You must be signed in to change notification settings - Fork 0
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
Enhance docstrings and add examples #25
Comments
I prefer this format over our current. What do you think @sophiamaedler? |
@namsaraeva is suggesting Google docstring format instead of numpy. |
I'm fine with either. What's the preferred standard in scverse packages at the moment? Would be good if we could implement some sort of check when adding new commits after switching to make sure that all doc strings are in the chosen format. We had some mismatched formats in the past that I went through and homogenized. |
It's numpy by default but many use Google (e.g. me). It's more or less a 50/50 split.
No worries, I got you :) |
Then let's go with Google :-) Let me know if you need help with something. |
this should be addressed as part of #43 |
We should check all docstring so that they match in the format. Add examples where needed.
The text was updated successfully, but these errors were encountered: