-
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 #434 remove pharmaversesdtm dependency #439
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.
CAn you just put a note in the news so we know when this was removed from admiraldev please?
@millerg23 these checks are falling over I think related to tibble?? |
@bms63 we don't import |
yeah - i think we removed that one recently from suggests?? thanks for fixing!! |
.....now im wondering if it is wise to deviate between admiral and admiraldev with tibble stuff??? Just might be confusing for team?? |
yeah I know what you mean, does seem inconsistent. Perhaps a separate ticket and discuss at next meeting? |
Yeah - I think we should add tibble back - honestly I think we should just match to admiral. We have this styler ticket as well. Could you make a new ticket and tag the team for discussion. |
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()