We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Date.parse("e 3") Thu Mar 01 2001 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("zzz 3") Thu Mar 01 2001 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("3") Sun Mar 01 2015 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("3th") Sun Mar 01 2015 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("zzzzzzzzzz 3th") Thu Mar 01 2001 00:00:00 GMT-0800 (Pacific Standard Time)
The text was updated successfully, but these errors were encountered:
wow, that's just... huh. Looks like it's seeing 3 and picking March (sort of right... sorta... a method to the madness at least)
Going on record: I hate this parser implementation. That's going to be the big v2 change I feel...
Sorry, something went wrong.
I've spent some time trying to bend the parser to my will and it's been slow going... I can totally get behind that :).
No branches or pull requests
Date.parse("e 3")
Thu Mar 01 2001 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("zzz 3")
Thu Mar 01 2001 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("3")
Sun Mar 01 2015 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("3th")
Sun Mar 01 2015 00:00:00 GMT-0800 (Pacific Standard Time)
Date.parse("zzzzzzzzzz 3th")
Thu Mar 01 2001 00:00:00 GMT-0800 (Pacific Standard Time)
The text was updated successfully, but these errors were encountered: