assign_datetime algorithm
#47
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update `hardcode_no_ct()` by allowing the rewriting of the `target_sdtm_variable` variable to preserve `NA`
* hardcode_no_ct algorithm code changes * harcode_ct working as expected * assign_ct and assign_no_ct works great. * address review comments
Merge branch 'main' into 0040_hardcode_no_ct # Conflicts: # DESCRIPTION # NAMESPACE # inst/WORDLIST
- Adds three new user facing ct-related functions: `read_ct_example()`, `ct_example()` and `read_ct()` - Provides a ct example file in inst/ct/
… calling functions
… into 0040_hardcode_no_ct
As it is no longer needed.
Export `ct_vars()` such that we can cross-reference it from other functions' documentation.
- `ct` to `ct_spec` (ct specification) - `cl` to `ct_cltc` (codelist code)
As per @rammprasad's suggestion.
Merge branch 'main' into 0046_assign_datetime # Conflicts: # DESCRIPTION # NAMESPACE # NEWS.md # _pkgdown.yml
- This bug is related to the support of input is in two different variables (date and time). - A unit test was also added
rammprasad
approved these changes
May 14, 2024
edgar-manukyan
approved these changes
May 14, 2024
There was a problem hiding this comment.
Thanks so much @ramiromagno 💯 ⭐ ⭐ ⭐, very nice job. Awesome tests.
I left a super-minor suggestion in case you want to consider.
Credit goes to @edgar-manukya for the expression
`ct_spec_vars()` used to be an internal function but not anymore: so no need for `:::`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 oak 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
develbranch until you have checked off each task.Request Title (Use Edit button in top-right if you need to update)
tidyverse style guide. Run
styler::style_file()to style R and Rmd filesconsider realistic data scenarios and edge cases, e.g. empty datasets, errors,
boundary cases etc. - See
Unit Test Guide
fully follow the
deprecation guidance?
and families. Refer to the
categorization of functions to tag appropriate keyword/family.
devtools::document()so all.Rdfiles in themanfolder and theNAMESPACEfile in the project root are updated appropriatelyNEWS.mdif the changes pertain to a user-facing function (i.e. ithas an
@exporttag) or documentation aimed at users (rather than developers)pkgdown::build_site()and check that all affectedexamples are displayed correctly and that all new functions occur on the "Reference" page.
lintr::lint_package()R CMD checklocally and address all errors and warnings -devtools::check()