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
Today I discovered a bug related to the use of "3 months ago". In this case, the resultant dataset is for a single day three months ago (8/12/12). I would expect to see all payments for August.
Looking into the tests I see this case:
{
description => '3 months ago from June 15 is March 15',
date_range_string => '3 months ago',
as_of => '2013-06-15',
beg => '03/15/2013 12:00AM',
end => '03/15/2013 11:59PM',
}
Clearly, the choice to make this a single day 3 months ago is deliberate. I don't know if there is a fix for this, but something to consider.
The text was updated successfully, but these errors were encountered:
I'm currently inclined to leave the behavior as-is. In my mind, "3 months ago" refers to a precise point in time, whereas "last month" and "next month" more generally refer to the entirety of a specific month.
This is mostly because I use "[n] months ago" searches fairly often to review email and whatnot, so that may just be a personal bias. I'm going to leave this open for now in case anyone else has opinions on the topic. (This assumes that people use D::RP::EN, which is perhaps a bit of a stretch.)
I received an internal bug report today stating:
Looking into the tests I see this case:
Clearly, the choice to make this a single day 3 months ago is deliberate. I don't know if there is a fix for this, but something to consider.
The text was updated successfully, but these errors were encountered: