Dealing with cases like '2 Nov 10' #260
Merged
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
Sometimes separators like slashes or dashes are not present and still the date is 'readable': parsing '2 Nov 10' should be the same than parsing 'Nov 2nd, 2010', isn't it?
|
...I meant, in terms of results: same date for both cases. |
leejarvis
added a commit
that referenced
this pull request
May 15, 2014
…arator_off Dealing with cases like '2 Nov 10'
|
Looks good thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes separators like slashes or dashes are not present and
still the date is 'readable': parsing '2 Nov 10' should be the
same than parsing 'Nov 2nd, 2010', isn't it?