search

bdauer / tasktracker

tracker for one-off, timed and recurring tasks scheduled for or due on a given day.
2 stars 0 forks source link

Update the model for additional task end states #38

Closed bdauer closed 7 years ago

bdauer commented 7 years ago

Currently the only way for a task to end is by being completed.

This is a problem because someone may, e.g. want to disable a task, or a task may be failed (failure should be possible at least for timed recurring tasks (maybe think about a failable option for all tasks)).

After graphing out the possibilities, these seem to cover the end states I can think of: disabled, failed, completed. So I need to add the first two to my task model and update the logic that's checking on whether or not a task has been completed as relevant.

bdauer commented 7 years ago

Alternatively, instead of disabling a task, I could have a delete option.

In the case of recurring tasks, I can set it to only delete new recurrences, not past ones. That way there's still a record for the time that it was running.

bdauer commented 7 years ago

There's a disabled and completed option now. I'm going to leave the failed option for after I get the web app up and running.