-
Notifications
You must be signed in to change notification settings - Fork 79
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
parseTimeM succeeds on hours/minutes greater than specified in documentation #70
Comments
@AshleyYakeley do you think this is an issue or are there cases where the time parser should accept "99:99" as input? |
Starting to look briefly at this. I will report back any progress I make. |
I have a fix for it n my forked repo, but I don't know enough about the quirks of time, and by this i don't mean the library, but what time values are reasonable or not, to file a pull request without any feedback. This is one of the most depended on libraries so i don't want to be hasty with a change, as it possibly affects a lot of people |
Okay, I will not look further into this. I am happy to comment on any PRs your make (maybe from a branch to master within your fork as a first pass review?). |
fix merged |
The documentation for the format strings says
but while
Succeeds/Fails correctly, the following
Succeed - with hours/minutes I would not consider correct.
I would expect
parseTimeM
to have the property "if it is parseable then the formatted string is equal to the initial string".The text was updated successfully, but these errors were encountered: