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

catch main up to dev, epiprocess 0.9.0 #530

Merged
merged 180 commits into from
Sep 27, 2024
Merged

catch main up to dev, epiprocess 0.9.0 #530

merged 180 commits into from
Sep 27, 2024

Conversation

dshemetov
Copy link
Contributor

Checklist

Please:

  • Make sure this PR is against "dev", not "main" (unless this is a release
    PR).
  • Request a review from one of the current main reviewers:
    brookslogan, nmdefries.
  • Makes sure to bump the version number in DESCRIPTION. Always increment
    the patch version number (the third number), unless you are making a
    release PR from dev to main, in which case increment the minor version
    number (the second number).
  • Describe changes made in NEWS.md, making sure breaking changes
    (backwards-incompatible changes to the documented interface) are noted.
    Collect the changes under the next release number (e.g. if you are on
    1.7.2, then write your changes under the 1.8 heading).
  • See DEVELOPMENT.md for more information on the development
    process.

Change explanations for reviewer

Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch

brookslogan and others added 30 commits June 12, 2024 16:43
from breaking changes or deprecations
- Correct check for whether data masking was used
- Update checks and error messages for currently-accepted kinds of objects
- Make some variable naming more consistent between files
brookslogan and others added 29 commits September 13, 2024 19:15
Also move some things to @Keywords internal to match some recent additions,
though it's still a mix.
Don't use deparse approach for now as it outputs ugly things like
`structure(..........)` for multiple time classes and probably other classes. In
the future, we may want to do something like a backport of deparse1 + special
cases for time&other classes, for easier copy-paste for debugging while keeping readability.
Modern tidyselect distinguishes itself from data masking and prefers not having
.data$, so just drop it. Attempt to appease linter with more globalVariables().
* key_colnames order change
* replace kill_time_value with exclude arg in key_colnames
* move duplicate time_values check in epi_slide
@dshemetov dshemetov merged commit 7bf94e3 into main Sep 27, 2024
8 checks passed
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.

6 participants