You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we expect users to appropriately tidyr::complete their data appropriately before using with some epiprocess functionality, but complete on epi_dfs drops epi_df-ness; we should stop that from happening. (If we were to enforce key uniqueness, this might need to be done carefully or with some additional checks, but since we don't, it's probably just unconditionally reclassing or dplyr_reconstructing).
The text was updated successfully, but these errors were encountered:
This might be a tool to use in #256; if we want to complete slide inputs, we may need a complete / gap-filling method for that works across both epi_dfs and tibbles (depending on whether our slide inputs have been decayed into tibbles or are still epi_dfs). tidyr::complete may or may not work for this already, but it's probably what we want to use. We're trying to avoid heavy tidyverts dependencies now.
Currently, we expect users to appropriately
tidyr::complete
their data appropriately before using with someepiprocess
functionality, butcomplete
onepi_df
s dropsepi_df
-ness; we should stop that from happening. (If we were to enforce key uniqueness, this might need to be done carefully or with some additional checks, but since we don't, it's probably just unconditionallyreclass
ing ordplyr_reconstruct
ing).The text was updated successfully, but these errors were encountered: