-
-
Notifications
You must be signed in to change notification settings - Fork 680
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
No error raised on invalid dates #519
Comments
I would like to tackle this. Any suggestions on where I can start? |
Actually, errors are raised for invalid dates that are correctly formatted: Notice that your output just points to January 1st of that year. There is a bug with parsing dates in that format. Either these dates need to be correctly parsed (and then the invalid date error can be raised), or dates in this format need to have the same effect as:
|
Good point. For consistency, which do you think is the best way to tackle this? |
I would count dates in the format "MM/DD/YYYY" as invalid for now. |
It seems like an error should be thrown on invalid dates, but this doesn't appear to happen. Is there some parameter I need to pass in to the
get()
function to enforce these are checked properly?Using v0.12.1:
The text was updated successfully, but these errors were encountered: