Last modified: 2014-04-01 12:27:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64730, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62730 - TimeParser should return correct precision when only month and year or year is given
TimeParser should return correct precision when only month and year or year i...
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: High major (vote)
: ---
Assigned To: Wikidata bugs
u=dev c=backend p=8 s=2014-03-18
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-17 13:49 UTC by tobias.gritschacher
Modified: 2014-04-01 12:27 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description tobias.gritschacher 2014-03-17 13:49:51 UTC
Currently, when trying to parse something like "December 2012" and precision "day", the Time Parser returns "+0000000000000012-12-00T00:00:00Z" and precision "11" which is the wrong precision, because it indicates a day but instead should indicate a month. The correct return would be "10" (if the parser is smart) or at least it should fail to parse.
Comment 1 Addshore 2014-03-21 10:30:37 UTC
It looks like this is in DataValues/Time
Comment 2 Addshore 2014-03-21 12:22:21 UTC
https://github.com/DataValues/Time/pull/10
Comment 3 Gerrit Notification Bot 2014-03-21 12:24:41 UTC
Change 119980 had a related patch set uploaded by Addshore:
Use DataValues/Time version ~0.5.0

https://gerrit.wikimedia.org/r/119980
Comment 4 Gerrit Notification Bot 2014-03-24 14:27:44 UTC
Change 119980 merged by Addshore:
Use DataValues/Time version ~0.5.1

https://gerrit.wikimedia.org/r/119980

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links