Overdue Chores Fix #51
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Wallexus <167881799+Wallexus@users.noreply.github.com>
Signed-off-by: Wallexus <167881799+Wallexus@users.noreply.github.com>
|
Oh, almost forgot: this also changes |
|
@bmcclure Hi Ben. Thanks for the cool tool. Are there any plans for another release, hopefully including this fix? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As requested in #33, this is my attempt to fix #33. It's been quite some time, but I think essentially
everychores were bypassing a check incalculate_day1, becausetodayis calculated past midnight. I've left the check in, because I had trouble understanding the complete flow and added an additional check forday1 == start_date == last_completed, which will just incrementday1.I would appreciate, if this can be double-checked, but I've used this implementation for ~10 months now and never encountered this issue again.