Currently, we require dates to be input in the format 1789-12-01, but behavior is undefined if you include times like 1997-07-16T19:20:30+01:00. The time parser should be able to handle rounding of things like time of day and plotting down to the minute level. (This would be useful for Twitter archives, among other things).
It would be nice if it didn't break on human readable but technically incorrect formats: 2015-1-29 is a reasonable way for somebody to write a date in their jsoncatalog.txt file, even if technically it should be 2015-01-29.
Currently, we require dates to be input in the format
1789-12-01
, but behavior is undefined if you include times like1997-07-16T19:20:30+01:00
. The time parser should be able to handle rounding of things like time of day and plotting down to the minute level. (This would be useful for Twitter archives, among other things).It would be nice if it didn't break on human readable but technically incorrect formats:
2015-1-29
is a reasonable way for somebody to write a date in theirjsoncatalog.txt
file, even if technically it should be2015-01-29
.