Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Strings validated against the "date-time" format should not be required to have a millisecond element #42

Closed
davewatts opened this issue Jun 22, 2013 · 2 comments
Closed

Strings validated against the "date-time" format should not be required to have a millisecond element #42

davewatts opened this issue Jun 22, 2013 · 2 comments

Comments

@davewatts
Copy link
Contributor

Currently date strings in the format YYYY-MM-DDT00:00:00Z are considered invalid as they are missing a millisecond element.

Looking at http://tools.ietf.org/html/draft-zyp-json-schema-03 and http://tools.ietf.org/html/rfc3339#section-5.6 it seems to me that the millisecond element should be optional.
tdegrunt added a commit that referenced this issue Jun 22, 2013
@tdegrunt
Merge pull request #43 from egrove/master
2f5f1a9 
Fix for issue #42; Milliseconds optional for "date-time" format.
@tdegrunt
Copy link
Owner

Should be done, closing ... :)

@davewatts
Copy link
Contributor Author

Thanks for the speedy acceptance 👍

@awwright awwright mentioned this issue Aug 2, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tdegrunt @davewatts