Fix #53 Completing a task multiple times with "Reschedule from completion date" pushes it further into the future
This commit is contained in:
parent
472e78fc5e
commit
b9160bf681
1 changed files with 0 additions and 8 deletions
|
@ -42,14 +42,6 @@ func scheduleNextDueDate(chore *chModel.Chore, completedDate time.Time) (*time.T
|
||||||
baseDate = time.Date(baseDate.Year(), baseDate.Month(), baseDate.Day(), t.Hour(), t.Minute(), 0, 0, t.Location())
|
baseDate = time.Date(baseDate.Year(), baseDate.Month(), baseDate.Day(), t.Hour(), t.Minute(), 0, 0, t.Location())
|
||||||
|
|
||||||
}
|
}
|
||||||
if chore.IsRolling && chore.NextDueDate.Before(completedDate) {
|
|
||||||
// we need to check if chore due date is before the completed date to handle this senario:
|
|
||||||
// if user trying to complete chore due in future (multiple time for insance) due date will be calculated
|
|
||||||
// from the last completed date and due date change only in seconds.
|
|
||||||
// this make sure that the due date is always in future if the chore is rolling
|
|
||||||
|
|
||||||
baseDate = completedDate.UTC()
|
|
||||||
}
|
|
||||||
|
|
||||||
if chore.FrequencyType == "daily" {
|
if chore.FrequencyType == "daily" {
|
||||||
nextDueDate = baseDate.AddDate(0, 0, 1)
|
nextDueDate = baseDate.AddDate(0, 0, 1)
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue