-
Notifications
You must be signed in to change notification settings - Fork 63
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 #2143 Loosen restrict_derivation()
assertion
#2144
Conversation
Merge branch 'main' into 2143_restrict_derivation_lighten_assertion # Conflicts: # DESCRIPTION # NEWS.md
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.
Do any of the vignettes or documentation need to be changed for this update? I thought we said this wasn't allowed somewhere?
Don't recall that portion, I imagine we should be okay, I would not say its particularly intuitive to call mutate using this either, had a hard time coming up with an appropriate test, I will say I did miss a roxygen blurb |
R/restrict_derivation.R
Outdated
@@ -12,7 +12,7 @@ | |||
#' The function must provide the `dataset` argument and all arguments | |||
#' specified in the `params()` objects passed to the `arg` argument. | |||
#' | |||
#' Please note that it is not possible to specify `{dplyr}` | |||
#' Please note that it is not advised to specify `{dplyr}` |
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.
@bms63 Was it this that you meant?
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.
Umm...is this saying not to do dplyr::mutate()
?
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.
Well I'm not quite sure the origin story of this one, but all we wanted to do was loosen up the restriction such that we allow functions that don't necessarily have "dataset" as an argument. Sounds like there was a firm decision to outright not-allow dplyr
functions or at least explicitly say they don't work since they don't file under the original restriction, but after lifting it, might lead to loosened/unintended-usage by users.
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.
@bundfussr any memory of this one?
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 far as I remember this sentence was added after the last clean-up to point out that dplyr
functions can not be used. As this is changed now, we should remove the sentence completely.
NEWS.md
Outdated
@@ -4,10 +4,13 @@ | |||
|
|||
## Updates of Existing Functions | |||
|
|||
- `restrict_derivation()` now allows `dplyr` functions like `mutate` in the `derivation argument (#2143) |
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.
Should be `{dplyr}`
instead of `dplyr`
. Then it is autolinked.
if (!is.null(args)) { | ||
assert_function(derivation, names(args)) | ||
} |
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 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 don't know if that is necessary. I feel like the original purpose of the assertion, was to check if all the appropriate necessary arguments were provided for that specific function. And the developer would likely know what is needed for that hard-check when using the assertion.
Many functions that use ...
still have other necessary arguments anyway, so they can also just run assert_function(dev_fun)
without checking params, to ensure it is a function. The remainder of that function, dev_fun
in this case, should provide the appropriate errors/message handling if something is plugged in incorrectly.
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 think the intention of the check was to ensure that all arguments specified for args
are arguments of the function specified for derivation
.
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.
Well I suppose it is a relatively short implementation, I can make an appropriate issue for it
…github.com/pharmaverse/admiral into 2143_restrict_derivation_lighten_assertion
Closing in favor of #2164 |
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
devel
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
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()