-
Notifications
You must be signed in to change notification settings - Fork 6
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
Closes #468 multiple units: extend required_unit argument in assert_unit() #471
Conversation
Good catch! |
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.
Great job @bundfussr! No other comments from my end.
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.
Minor suggestion in NEWS.md but looks good otherwise.
NEWS.md
Outdated
@@ -2,6 +2,10 @@ | |||
|
|||
## Updates of Existing Functions | |||
|
|||
- The `required_unit` argument of `assert_unit()` has been enhanced. It is now | |||
possible to specify more than one unit or not specifying it. In the latter case |
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.
possible to specify more than one unit or not specifying it. In the latter case | |
possible to specify more than one unit or not specify it at all. In the latter case |
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.
Updated
@bundfussr I have nothing to add. Feel free to merge after considering the suggestions. Looks a few are still outstanding. Many thanks for pushing this through so quickly and @yurovska for great review!! |
I’m unfortunately not able to resolve conversations as I don’t have corresponding button (likely don’t have permission), but I’m happy with all updates made. @bundfussr Please feel free to close them all. |
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the
main
branch until you have checked off each task.styler::style_file()
to style R and Rmd filesdevtools::document()
so all.Rd
files in theman
folder and theNAMESPACE
file in the project root are updated appropriatelyNEWS.md
under the header# admiral (development version)
if the changes pertain to a user-facing function (i.e. it has an@export
tag) or documentation aimed at users (rather than developers)pkgdown::build_site()
and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.lintr::lint_package()
R CMD check
locally and address all errors and warnings -devtools::check()