-
Notifications
You must be signed in to change notification settings - Fork 46
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
Build documentation with the --nitpicky
option
#334
Conversation
Reviewer's Guide by SourceryThis pull request enables the File-Level Changes
Tips
|
Here's the code health analysis summary for commits Analysis Summary
|
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.
Hey @tovrstra - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
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.
I didn't go through it in much detail but what I saw looked good to me.
Thanks for checking. There are indeed a lot of mechanical changes. The main goal is the change in the configuration files. All the nitty-gritty is just needed to make the tests pass (and fix links in the docs). |
This is one more step in the list in #313, and also a continuation of #333, just tightening the screws a little...
The
--nitpicky
option of Sphinx may seem nitpicking. However, when not switched on, Sphinx happily ignores broken references in the documentation. As a result, we had many of these. To clean things up, the configuration of sphinx extensions (for api documentation) also had to be improved. I've also gone through allNDArray
type hints to specify them as float or int where this was applicable.Summary by Sourcery
This pull request enhances the documentation build process by enabling the
--nitpicky
option in Sphinx, improving the configuration of Sphinx extensions, and updating type hints forNDArray
to specify float or int where applicable. These changes ensure stricter validation of documentation references and improve type clarity.--nitpicky
option in Sphinx to ensure all references in the documentation are valid, preventing broken references from being ignored.NDArray
to specify float or int where applicable, enhancing type clarity and correctness.--nitpicky
option, ensuring that broken references are caught during continuous integration.--nitpicky
option, ensuring stricter validation of documentation references.