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.

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

Fixes Bug 62730 #10

Merged
merged 3 commits into from
Mar 21, 2014
Merged

Fixes Bug 62730 #10

merged 3 commits into from
Mar 21, 2014

Conversation

addshore
Copy link
Contributor

See https://bugzilla.wikimedia.org/show_bug.cgi?id=62730

Before this change if 2012-02-00 was passed in with
precision of a DAY as an opt the TimeValue would have
the precision of a DAY.
Now instead this will fall back to the precision of
a MONTH

* Removed TimeParser::SIGN_PATTERN constant
* Removed TimeParser::TIME_PATTERN constant
* Fix [bug 62730](https://bugzilla.wikimedia.org/show_bug.cgi?id=62730) TimeParser should return correct precision when only month and year or year is given
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bad grammar for the last point.

Fixed [bug 62730](https://bugzilla.wikimedia.org/show_bug.cgi?id=62730). The TimeParser now returns the correct precision when only month and year or year is given

JeroenDeDauw added a commit that referenced this pull request Mar 21, 2014
@JeroenDeDauw JeroenDeDauw merged commit 93b027b into master Mar 21, 2014
@JeroenDeDauw JeroenDeDauw deleted the bug62730 branch March 21, 2014 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants