Dāvis

why `month` should return end of month? it's actually not supported and that it returns anything at all is just pure luck. for now you can use ``` ruby Chronic.parse("1...

FYI, I've started on rewrite a while ago, see my comment on #316

It is known issue that Chronic doesn't work correctly when DST is involved, there are loads of such issues. There isn't really much you can do about it as Chronic...

I can't reproduce it and I suspect it's DST related, can you show example of how you parse it and which timezone is used?

It's definitely DST related bug. For me with EET timezone it's `Chronic.parse('2016-03-27 12am')` which gives nil and not your time. ``` Handler: handle_sy_sm_sd Handler-class: Chronic::RepeaterDayPortion --(2016-03-27 00:00:00 +0200..2016-03-27 11:59:59 +0300)...

because DST change happens only in that day, in other day it moves -1h back thus same hour appears twice and it does exist unlike in this case.

you need add `:guess => :begin` option like `Chronic.parse('today at 9:00 am', :guess => :begin)` it's because current Chronic version gets interval and takes middle of it but it did...

It's that way only because it was that way before, I mean with current `Chronic.parse('today')`, if I change to `:begin` then it won't match previous behavior but yeah I agree...

btw about that work I did on rewrite branch see #278

yeah, it's a bug, it's fixed in my `rewrite` branch but that's not ready yet and will be released as next major version.