Auto-expired requests falling off a day early #22

Closed
opened 2019-10-21 01:18:01 +00:00 by danieljsummers · 1 comment
danieljsummers commented 2019-10-21 01:18:01 +00:00 (Migrated from github.com)

This looks very similar to #17, but in the opposite direction. That issue made the items compare on dates, and the net effect was that the day a request is entered should be 0-day; a request entered on one Sunday (the 1st), with expiration at 14 days, should still be on the list 2 weeks from that day (both the 8th and 15th), but fall off the following Monday (the 16th).

Make the query and the "am I expired?" code match this behavior.

This looks very similar to #17, but in the opposite direction. That issue made the items compare on dates, and the net effect was that the day a request is entered should be 0-day; a request entered on one Sunday (the 1st), with expiration at 14 days, should still be on the list 2 weeks from that day (both the 8th and 15th), but fall off the following Monday (the 16th). Make the query **and** the "am I expired?" code match this behavior.
danieljsummers commented 2022-08-07 23:52:32 +00:00 (Migrated from github.com)

Closing this in preference to #41

Closing this in preference to #41
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bit-badger/PrayerTracker#22
No description provided.