Skip to content

Conversation

@richardjrossiii
Copy link
Contributor

This was causing sporadic issues when the server returns dates that are valid according to the ISO standard, but not according to DateTime.ParseExact.

Fixes #64.

This was causing sporadic issues when the server returns dates that are valid according to the ISO standard, but not according to DateTime.ParseExact.

Fixes #64.
@hallucinogen
Copy link
Contributor

LGTM. This was a bug from 2 years ago, right? I thought we fixed it :/

@richardjrossiii
Copy link
Contributor Author

@hallucinogen It recently showed up again. We're not 100% sure why. Still better to have it than not.

richardjrossiii added a commit that referenced this pull request Dec 3, 2015
…strict

Support any number of trailing zeroes when decoding dates.
@richardjrossiii richardjrossiii merged commit 82b76c4 into master Dec 3, 2015
@richardjrossiii richardjrossiii deleted the richardross.datetimeformat.strict branch December 3, 2015 20:00
@richardjrossiii richardjrossiii added this to the 1.7.0 milestone Jan 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants