Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up
Hello.
It would be nice to have a cutoff parameter for commands such as dmy().
It's quite common to deal with dates stored as 31-12-40 or 12/31/70 where the year is stored with just 2 digits. That's a bad way to do it but there are many databases like that.
If you just use lubruidate commands to convert that strings to dates the user can get unexpected results.
And what's more serious, it can even miss he is having a problem till is too late.
The user can transform the data by doing:
or
But this would need to be modyfied depending on the exact formats the user has and wants, and it's prone to error and takes a lot of code for a simple task.
Could you please add a "cutoff" date parameter to lubridate functions to allow the user to just do
dmy(mydates, cutoff=20)when he wants to consider numbers bellow 20 as 20xx and numbers above 20 as 19xx, please?I think it should be easy because somewhere you already do it, you just need to expose that parameter to the user.
And I think it would be very useful.
I will also allow to easily use the same syntax across different libraries.