You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi ,
It seems like that Chronic.parse("3 months ago") doesn't use Rails built-in time parse function or like that. It seems like Chronic uses 30 days as a unit to calculate months, which is really not good.
Let's say, i.e:
today is 2011/05/30,
well ,using Chronic.parse("3 months ago") will get 2011/03/02( just minus 90 days) , but obviously it is not what we want.
And if you use Rails built-in time support, "3.months.ago" will get 2011/02/28 which is exactly what we want.
Any thought?
Thanks
The text was updated successfully, but these errors were encountered:
Have you tried using the main fork of Chronic? This branch of mine hasn't been updated in quite some time. I recommend trying the main fork at mojombo/chronic, and if you are still experiencing problems, opening a ticket there.
Hi ,
It seems like that Chronic.parse("3 months ago") doesn't use Rails built-in time parse function or like that. It seems like Chronic uses 30 days as a unit to calculate months, which is really not good.
Let's say, i.e:
today is 2011/05/30,
well ,using Chronic.parse("3 months ago") will get 2011/03/02( just minus 90 days) , but obviously it is not what we want.
And if you use Rails built-in time support, "3.months.ago" will get 2011/02/28 which is exactly what we want.
Any thought?
Thanks
The text was updated successfully, but these errors were encountered: