-
Notifications
You must be signed in to change notification settings - Fork 207
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
as_date no longer supports argument "format" #607
Comments
Well, technically format argument was never part of the API, and it worked for character vectors because in 1.6.0 it did as.Date. In 1.7.0 a range of issues with character parsing were fixed (#598, #597, #536) and that means On your string, the simplest |
Thanks for the quick response. For my needs, I replaced it with as.Date, so I'm fine. Thank you for the other suggestions. |
as_date is advertised as drop-in replacement for as.Date. I will try to fix this. |
Note that |
I think, the best is to leave format argument to character methods as before. The issues is that lubridate parsers are not equivalent to strptime and one would need to treat this particular case specially and redirect it to strptime internally. This is how I plan to fix this at the moment. |
The argument |
It is supported. |
Humm.... I feel bad now, it was a bug on my side, sending a numeric vector (for which format isn't supported, which makes sense) vs a character vector for which it is... my bad, sorry, I'm so used to work with date as characters... |
Between versions 1.6.0 and 1.7.1, the function as_date lost the ability to use the argument "format". I was using this when the date was embedded in part of the text.
the command
returns an error in 1.7.1
The text was updated successfully, but these errors were encountered: