cmu-delphi / cmu-delphi/epiprocess
Do we still need `clone.epi_archive`?
Open
- Dominant language
- R
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
`clone.epi_archive` mostly just applies `data.table::copy` to the underlying data.table object. Is that still needed, post the R6 refactor?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the `clone.epi_archive` entry point and reviewing how it applies `data.table::copy` to the underlying object after the R6 refactor. Compare its current behavior with the surrounding clone API and determine whether the method should be retained, removed, or changed; done means the issue has a clear decision and any affected behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100