-
Notifications
You must be signed in to change notification settings - Fork 47
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
Support Dates #13
Comments
Updated to 1.1 and it seems to be good now. Oops! |
Hmm - I'm not sure what v1.1. did to address that to be honest. I wonder if you could write a test for it? |
I was mistaken when I closed it out. I can write a test and fix later today. |
make that tomorrow afternoon. |
It seems like JavaScript doesn't have any good cross-browser method of parsing an ISO date string. http://stackoverflow.com/questions/5802461/javascript-which-browsers-support-parsing-of-iso-8601-date-string-with-date-par |
What about some kind of plugin system that gives handlers a chance to try to deal with the value before it's returned. Then we can have other features that people can include if need be. Or we could recommend using unix time and handle those explicitly? Sent from my iPhone
|
I had considered UNIX time, but it is hard to discern between a number and UNIX time. It would require user intervention after parsing to get Date objects. |
When Arg.stringify comes across a Date object it falls on its face: http://jsfiddle.net/JVECJ/
https://github.com/stretchr/arg.js/blob/master/src/arg.js#L127 needs to additionally have an instanceof check for
Date
.The text was updated successfully, but these errors were encountered: