This repository has been archived by the owner on Apr 2, 2019. It is now read-only.
#32 Handle null, undefined and incorrect values in DatetimeFormatter #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…atetimeFormatter
wyuenho
added a commit
that referenced
this pull request
Feb 5, 2013
#32 Handle null, undefined and incorrect values in DatetimeFormatter
|
Thank you very much |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a new pull request for #32
I'm not sure exactly how you prefer to deal with incorrect data - at the moment I added code to treat them as an empty string, which ends up turning them into the "minimum date'' of 1899-12-31T00:00:00Z.
Depending on your opinion, another option would be to throw an exception instead, when the data is obviously invalid.