-
Notifications
You must be signed in to change notification settings - Fork 659
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
Document the usage of NoDataError
in it's docstring
#4359
Document the usage of NoDataError
in it's docstring
#4359
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.
Hello there first time contributor! Welcome to the MDAnalysis community! We ask that all contributors abide by our Code of Conduct and that first time contributors introduce themselves on the developer mailing list so we can get to know you. You can learn more about participating here. Please also add yourself to package/AUTHORS
as part of this PR.
Linter Bot Results:Hi @HeetVekariya! Thanks for making this PR. We linted your code and found the following: There are currently no issues detected! 🎉 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4359 +/- ##
==========================================
Coverage 93.37% 93.37%
==========================================
Files 170 184 +14
Lines 22340 23452 +1112
Branches 4085 4085
==========================================
+ Hits 20859 21898 +1039
- Misses 963 1036 +73
Partials 518 518 ☔ View full report in Codecov by Sentry. |
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.
Thanks @HeetVekariya for taking on this issue. Docstrings in MDAnalysis are written to be read in two scenarios:
- In the code format you see here, e.g. if someone looks at this file or calls
help(NoDataError)
- In our rendered documentation.
In order for this docstring to be read nicely in our rendered documentation, it should be written in correct Sphinx (edit: reStructuredText) syntax. You can build the docs yourself by navigating to the package/doc/sphinx
folder: cd package/doc/sphinx && make html
. Alternatively, we build docs for pull requests that get re-built with each push. You can view those here: https://mdanalysis--4359.org.readthedocs.build/en/4359/documentation_pages/exceptions.html#MDAnalysis.exceptions.NoDataError
As you can see, the current formatting looks a bit odd. Could you please re-format using reStructuredText notation (e.g. using *
for bullet points and not indenting unnecessarily?)
Below I'll also comment on content.
(Apologies, got cut-off in the middle of review) @HeetVekariya looks like you might need to install the documentation dependencies, something like |
The docs generated are not good. |
|
Ah whoops, sorry, the following command might work better for you (in the
|
It looks like the lack of bullets is actually a bug in the Sphinx theme we're using for our documentation -- for some reason the list items here don't have bullets. I've raised an issue in the appropriate repo and will fix it there: MDAnalysis/mdanalysis-sphinx-theme#82 |
@HeetVekariya could you please add yourself to AUTHORS as this is your first contribution? |
LGTM -- thank you @HeetVekariya for fixing this long-standing issue! Congratulations on your first commit to MDAnalysis :-) |
|
Fixes #3901
Changes made in this Pull Request:
NoDataError
in it's docstring.PR Checklist
Developers certificate of origin
📚 Documentation preview 📚: https://mdanalysis--4359.org.readthedocs.build/en/4359/