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

Km compactify rectify #101

Merged
merged 114 commits into from
Jul 29, 2022
Merged

Conversation

kenmawer
Copy link
Contributor

I rectified compactify by overhauling it.

kenmawer added 30 commits May 13, 2022 16:08
@brookslogan
Copy link
Contributor

Closes #111. Closes #136.

@brookslogan
Copy link
Contributor

Closes #62.

Copy link
Contributor Author

@kenmawer kenmawer left a comment

Choose a reason for hiding this comment

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

Looks good to me. I'd say that on a separate PR, we can specify examples, etc. on vignettes about what things such as clobberable versions and the end version mean, if those aren't there.

@kenmawer kenmawer requested a review from brookslogan July 25, 2022 18:07
@brookslogan
Copy link
Contributor

Okay, discussing with Ryan, we might need to roll back some of my changes, at least.

@kenmawer
Copy link
Contributor Author

kenmawer commented Jul 25, 2022

The pull request is filled with random changes, which makes it hard to track down what had actually been changed within this pull request rather than outside of it. I may have overlooked something that should be updated/fixed, especially here with the clutter.

@brookslogan
Copy link
Contributor

The Files changed helps with this, or using commit1..commit2 or commit1...commit2 with git commands. Of course, it probably would have been better if for some of these incidental bugfixes if I just made checks for the edge cases they addressed and complained and made the fixes in separate PRs. Then we'd be able to merge more quickly and have less changes from merge conflict resolution to deal with.

To try to prevent this from continuing to get out of hand, I'll try to do the minimal immediate edits from Ryan's feedback and file others in issues.

lcbrooks and others added 4 commits July 27, 2022 04:12
Always introduce version-wise LOCF as "last observation of each observation
carried forward (LOCF)" or something quite similar.

Clarify time-wise LOCF in one place.
@kenmawer
Copy link
Contributor Author

kenmawer commented Jul 27, 2022

It noticed that by fixing the conflicts, the tests fail. Did I wrongly use the bottom part rather than the top part of the conflict?

kenmawer added 2 commits July 27, 2022 11:01
Merge branch 'main' of https://github.com/cmu-delphi/epiprocess into km-compactify_rectify

# Conflicts:
#	R/archive.R
#	tests/testthat/test-methods-epi_archive.R
Merge branch 'km-compactify_rectify' of https://github.com/dajmcdon/epiprocess into km-compactify_rectify

# Conflicts:
#	R/archive.R
#	tests/testthat/test-methods-epi_archive.R
@brookslogan
Copy link
Contributor

I'm looking at git log --remerge-diff and some minor point did pop up. I'll push changes for what I notice, then you can double-check. After that, maybe I'll just file the remaining issues Ryan brought up in Issues and merge so we don't have to keep merging main in here.

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.

Add option to compactify issue data in epi_archive
4 participants