migrate() would fail if values of time argument had overlapping characters (i.e., "T1" and "T100")
migrate() now throws a warning if the argument passed to time is a character-type columnfill_state argument to migrate() has been introduced, allowing users to migrate IDs that only exist at a single timepoint to a new or existing statestate argument of type character to type factordate argument in migrate() has been fully deprecated (replaced by time argument in v0.4.0)%>% has been replaced by the native pipe |> that was introduced in R 4.1. Due to this, the minimum R version required to install {migrate} has been bumped to R 4.1. Accordingly, {magrittr} was removed from Imports.dplyr::enquo and (!! var) in favor of the ({{ var }}) syntax.date argument in migrate() has been replaced (renamed) in favor of timeThe term date seemed too specific to use in the migrate() function, so it was replaced by the more general term, time. Instead of holding users to using Date-type column variables, this change allows them flexibility to migrate from Time A --> Time B, for example.
migrate() has a new verbose argument (logical TRUE/FALSE), which informs the user of the time horizon over which the migration is being calculated:migrate(
data = mock_credit,
id = customer_id,
time = date,
state = risk_rating
)
# > === Migrating from: `2020-06-30` --> `2020-09-30` ===
# > ... [output] ...
migrate(), renamed to statemigrate()migrate() defaults to percentage migration, instead of absolutemigrate()