-
Notifications
You must be signed in to change notification settings - Fork 85
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
Updated Readthedocs documentation in line with current practices. #2048
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2048 +/- ##
==========================================
- Coverage 98.39% 98.39% -0.01%
==========================================
Files 124 133 +9
Lines 12212 13060 +848
==========================================
+ Hits 12016 12850 +834
- Misses 196 210 +14 ☔ 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 @Kat-90. I've made some suggestions, mostly for rephrasing sentences to aid readability. Feel free to ignore them if you don't think they represent improvements.
1. Issues should be assigned to a main reviewer. Adding multiple | ||
reviewers to the pull request is encouraged to help share expertise. | ||
Please ask for help assigning reviewers if you need it. | ||
1. All reviewers are encouraged to add comments to the pull request. |
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.
The numbering in this section needs updating.
doc/source/Running-at-your-site.rst
Outdated
bin/improver-tests unit # runs unit tests | ||
bin/improver-tests --help # Prints out the help information |
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.
These lines are also on 133-134. I think they can be removed here to avoid duplication.
doc/source/Code-Style-Guide.rst
Outdated
As mentioned above, it is important to ensure that no other functionality | ||
than passing inputs into the plugin is done within the CLI layer. |
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.
As mentioned above, it is important to ensure that no other functionality | |
than passing inputs into the plugin is done within the CLI layer. | |
As mentioned above, it is important to ensure that no functionality | |
other than calling the plugin exists within the CLI layer. |
doc/source/Code-Style-Guide.rst
Outdated
So any checks on the data or requirements of inputs should be done in | ||
the plugin itself. |
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.
So any checks on the data or requirements of inputs should be done in | |
the plugin itself. | |
Any checks on the data or input requirements should be done in the plugin itself. |
doc/source/Code-Style-Guide.rst
Outdated
* Avoid putting any functionality within the CLI at all other than | ||
passing in arguments to the plugin, all functionality should be | ||
done within the plugin layer itself. |
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.
* Avoid putting any functionality within the CLI at all other than | |
passing in arguments to the plugin, all functionality should be | |
done within the plugin layer itself. | |
* Avoid adding functionality to CLIs beyond calling the relevant plugin, all other functionality should be added to the plugin itself. |
@@ -80,6 +75,7 @@ As a Reviewer: | |||
|
|||
* Does the code do what is supposed to? | |||
* Are errors handled appropriately? | |||
* Is the code written to be run efficiently? |
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.
* Is the code written to be run efficiently? | |
* Is the code efficient with respect to processing time and memory requirements? |
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.
There is also a typo under 5.d which could be corrected here:
Does the code do what is supposed to? -> Does the code do what it is supposed to?
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, I've changed both.
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 for these changes @Kat-90. I'm happy to approve this now.
Addresses https://github.com/metoppv/mo-blue-team/issues/795
This PR updates the best practices sections on the Readthedocs site in line with our current ways of working.
To build the webpages locally attempt the following: