Max-time should default to today when parsing the timestamp

[leonsodhi]

papertrail --min-time '12:30' --max-time '14:30' will return results after 14:30 today.

A workaround is to explicitly specify today:
papertrail --min-time '12:30' --max-time 'today 14:30'

[lmarburger]

That's odd. Chronic parses 24- and 12-hour times differently. It's 21:00 right now and "13:00" returns 1pm tomorrow but "1:00pm" returns 1pm today (8 hours ago).

[lmarburger]

>> Time.now                    #=> 2013-11-27 21:28:12 -0500
>> Chronic.parse '13:00'       #=> 2013-11-28 13:00:00 -0500
>> Chronic.parse '13:00 today' #=> 2013-11-27 13:00:00 -0500
>> Chronic.parse '1:00'        #=> 2013-11-27 13:00:00 -0500

[troy]

That is funny. Nice find. We may be using an ancient Chronic, for all I know.

[lmarburger]

As far as I can tell, I'm using the latest.

$ bundle show
Gems included by the bundle:
  * addressable (2.3.5)
  * bundler (1.3.5)
  * chronic (0.10.2)
  * faraday (0.8.8)
  * faraday_middleware (0.8.8)
  * multipart-post (1.2.0)
  * papertrail (0.9.7 0379be8)
  * rake (0.8.7)
  * yajl-ruby (1.1.0)

$ bundle outdated
Outdated gems included in the bundle:
  * faraday_middleware (0.9.0 > 0.8.8)
  * rake (10.1.0 > 0.8.7)