-
Notifications
You must be signed in to change notification settings - Fork 13
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
51 documentation updates v01 #56
Conversation
- Adds a new S3 class (cnd_df) for represented conditioned data frames, i.e. data frames that carry metadata about what records should be used for derivations - Adds support for basic pretty printing of cnd_df objects - Adds a user-facing function for creating such cnd_df objects: `condition_by` - Adds experimental "mutate"-version function for these conditioned data frames: `derive_by_condition()`
- Joins by raw and target data sets are now aware of conditioned tibbles - Transformation functions, namely `assign_datetime()`, `hardcode*()` and `assign*` are also conditioned-tibble aware - Unit test coverage for most cases indicated at #54 I believe the essential components are here to support the if_then_else algorithm via conditioned tibbles. Now, further testing, assertions and documentation is needed.
… help with template code Merge branch '0054-condition-by' into 51-documentation-updates-v01 # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
- Move `tgt_dat` to the first position in the argument list for cleaner command pipes. - Rename `condition_by()` to `condition_add()`. - Export `oak_id_vars()` for direct user access. - Update tidyselections to align with the latest practices.
Merge branch '0054-condition-by' into 51-documentation-updates-v01 # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
- Documentation - Examples - New article about cnd_df (WIP)
Merge branch '0054-condition-by' into 51-documentation-updates-v01 # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
Merge branch 'main' into 51-documentation-updates-v01 # Conflicts: # NAMESPACE # R/assign.R # R/assign_datetime.R # R/cnd_df.R # R/join.R # R/pipe.R # R/sdtm_join.R # _pkgdown.yml # inst/WORDLIST # man/condition_add.Rd # man/dot_pipe.Rd # man/mutate.cnd_df.Rd # man/tbl_sum.cnd_df.Rd # tests/testthat/test-assign.R # tests/testthat/test-cnd_df.R # tests/testthat/test-condition_add.R # tests/testthat/test-eval_conditions.R # tests/testthat/test-hardcode.R # tests/testthat/test-mutate_cnd_df.R # tests/testthat/test-pipe.R # vignettes/articles/cnd_df.Rmd
@edgar-manukyan @galachad @ramiromagno - I think all checks passed in the pipeline. But it is not showing up. Can you help me resolve this? From a content perspective, everything is complete. |
The |
Also, with R version 4.4 and more recent packages, I am also getting:
These warnings come from the functions implemented in the branch with conditioned data frames, and I know I have fixed them before we merged into main. So I guess this branch does not yet have the most up-to-date version of main integrated into it...? |
I have merged the latest main to this branch. Not sure what is going on. It doesn't show any differences. |
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.
@rammprasad All good. I just added one commit to update the WORDLIST.
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.
All good.
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
devel
branch 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.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. ithas an
@export
tag) 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 check
locally and address all errors and warnings -devtools::check()