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

Merging 'develop' into 'main' #416

Merged
merged 380 commits into from
Jun 22, 2022
Merged

Merging 'develop' into 'main' #416

merged 380 commits into from
Jun 22, 2022

Conversation

ddsjoberg
Copy link
Collaborator

@ddsjoberg ddsjoberg commented Jun 21, 2022

What changes are proposed in this pull request?

  • Merging the changes in the develop branch into the main branch

Checklist for PR reviewer

  • PR branch has pulled the most recent updates from main branch. Ensure the pull request branch and your local version match and both have the latest updates from the main branch.
  • If a new function was added, function should be included in _pkgdown.yml
  • If a bug was fixed, a unit test was added for the bug check
  • Run pkgdown::build_site(). Check the R console for errors, and review the rendered website.
  • Code coverage is suitable for any new functions/features. Review coverage with withr::with_envvar(new = c("NOT_CRAN" = "true"), covr::report()). Before you run, begin a fresh R session without any packages loaded.
  • R CMD Check runs without errors, warnings, and notes
  • usethis::use_spell_check() runs with no spelling errors in documentation
  • Has NEWS.md been updated with the changes from this pull request under the heading indicating the latest version. If there is an issue associated with the pull request, reference it in parentheses at the end update (see NEWS.md for examples).
  • Has the version number been incremented using usethis::use_version(which = "dev")
  • Has the README been knitted before merging to ensure each PR has the most up-to-date readme?
  • Approve Pull Request
  • Merge the PR. Please use "Squash and merge".

timtreis and others added 30 commits October 28, 2021 16:29
…dation

Add 'thevalidatoR' gh-action to generate a report on the release
Removed parcats from imports, moved DT and gt to suggests, updated mans
- added more tests for visr survfit
- updated visR to align with expectations
- default method should not be a test. It should provide a default way of plotting objects
bailliem and others added 20 commits June 10, 2022 16:45
)

* Add instruction to check if the readme has been rendered manually.

* build readme
* Updated estimate KM testing
Updated estimate KM documentation to ensure to user knows that we allow non-CDISC. This was not clear.

* Ran `usethis::use_tidy_description()` to put DESCRIPTION entries in standard order

* docs

* re-adding the error message that was removed.

* docs

Co-authored-by: shaesen2 <shaesen2@its.jnj.com>
Co-authored-by: Daniel Sjoberg <danield.sjoberg@gmail.com>
* doc updates

* doc updates
* Create Surv_CDISC.R

* updates

* doc update

* Re-build README.Rmd

* Update Surv_CDISC.R

* Re-build README.Rmd

* Update Surv_CDISC.R

* Re-build README.Rmd

* doc updates

* Re-build README.Rmd

* Update NAMESPACE

* merge conflict fix

* Re-build README.Rmd

* updates

* Re-build README.Rmd

* Update test-Surv_CDISC.R

* Re-build README.Rmd

* readme

* doc updates from review

* doc updates

* Update test-Surv_CDISC.R

* Update testing:
- consistent with CDISC philosophy
- check the actual requirement
- remove req T2.5 as this is not a requirement of our function, but something tested in the backend of survival

* removed requirement 2.3 in TOC

* change function name

* Update testing
Included CNSR info in estimate_KM to ensure user will restrict to 0/1

* re-documenting

Co-authored-by: GitHub Actions <actions@github.com>
Co-authored-by: Mark Baillie <bailliem@gmail.com>
Co-authored-by: shaesen2 <shaesen2@its.jnj.com>
Add questioning to functions under development / review
Move lifecycle badges to under description
Add questioning badge to tabelone
fix issues associated with apply_theme() function
@bailliem
Copy link
Collaborator

@ddsjoberg , @timtreis and @SHAESEN2 should we handle the interactive tutorial and any updates needed in a seperate issue?

@bailliem
Copy link
Collaborator

@ddsjoberg , @timtreis and @SHAESEN2 should we handle the interactive tutorial and any updates needed in a seperate issue?

It is already, missed this #418

@ddsjoberg ddsjoberg merged commit af91910 into main Jun 22, 2022
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.

8 participants