Skip to content
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 #2 hex logo and various other updates from default admiraltemplate #11

Merged
merged 9 commits into from
Feb 12, 2024

Conversation

rossfarrugia
Copy link
Collaborator

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.

  • Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
  • Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
  • Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
  • If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
  • Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
  • Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
  • Address any updates needed for vignettes and/or templates
  • Update NEWS.md under the header # admiralpeds (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)
  • Build admiralpeds site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the Reference page.
  • Address or fix all lintr warnings and errors - lintr::lint_package()
  • Run R CMD check locally and address all errors and warnings - devtools::check()
  • Link the issue in the Development Section on the right hand side.
  • Address all merge conflicts and resolve appropriately
  • Pat yourself on the back for a job well done! Much love to your accomplishment!

@rossfarrugia
Copy link
Collaborator Author

@bms63 @manciniedoardo a bunch more minor updates from the admiraltemplate defaults. let me know if you spot any others. FYI i did create #7 which catches some more needed for later once people dive into this.

Copy link

Code Coverage

Package Line Rate Health
admiralpeds 100%
Summary 100% (3 / 3)

Description: A toolbox for programming Clinical Data Standards Interchange Consortium
(CDISC) compliant Analysis Data Model (ADaM) datasets in R. ADaM datasets are a
mandatory part of any New Drug or Biologics License Application submitted to the
United States Food and Drug Administration (FDA). Analysis derivations are
implemented in accordance with the "Analysis Data Model Implementation Guide"
(CDISC Analysis Data Model Team, 2021, <https://www.cdisc.org/standards/foundational/adam/adamig-v1-3-release-package>).
(CDISC Analysis Data Model Team, 2021, <https://www.cdisc.org/standards/foundational/adam>).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we still need the year here? Wondering if we should drop that here and in other admiral packages?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes could probably be dropped - maybe best to have one person go through all and drop this in one go

@rossfarrugia rossfarrugia merged commit 0e3b712 into main Feb 12, 2024
14 of 17 checks passed
@rossfarrugia rossfarrugia deleted the 2_hex branch February 12, 2024 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants