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
Are there any plans to change condition handling for NA values so that their presence in a vector simply throws a warning versus an error? For instance...
anydate(c("20010101", "02/02/1902", NA))
... gives me the error:
Error in eval(substitute(expr), envir, enclos) : Inadmissable input: NA
I have gotten around this issue of parsing date formats while accounting for the presence of NA values by using lubridate::parse_date_time(), but think that adding such functionality to your package, combined with its parsing flexibility (and the keystrokes saved by not having to specify the orders parameter in parse_date_time()) would make it an extremely attractive option for daily use.
Thank you,
Mike
The text was updated successfully, but these errors were encountered:
Hello,
Are there any plans to change condition handling for
NA
values so that their presence in a vector simply throws a warning versus an error? For instance...anydate(c("20010101", "02/02/1902", NA))
... gives me the error:
Error in eval(substitute(expr), envir, enclos) : Inadmissable input: NA
I have gotten around this issue of parsing date formats while accounting for the presence of
NA
values by usinglubridate::parse_date_time()
, but think that adding such functionality to your package, combined with its parsing flexibility (and the keystrokes saved by not having to specify theorders
parameter inparse_date_time()
) would make it an extremely attractive option for daily use.Thank you,
Mike
The text was updated successfully, but these errors were encountered: