This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
Fix #3432 Recurring expenses spawn at UTC timing instead of local time #3570
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.
Pull request (PR) checklist
Please check if your pull request fulfills the following requirements:
Screen recording of your changes (if applicable):
No
What's changed?
Assume that on September 29, 2024, we create a recurring expense named
MyRecurrentExpense
. Consequently, an entry forMyRecurrentExpense
appears in theupcoming section
of the home screen for September 29. Previously, this entry was moved to theoverdue section
at 12:00 AM UTC rather than 12:00 AM local time. Now, the entry is moved to theoverdue section
at 12:00 AM local time.N.B: Expenses from September 29 will move to the
overdue section
on September 30 at 12:00 AM local time.Risk factors
What may go wrong if we merge your PR?
No
In what cases won't your code work?
No
Does this PR close any GitHub issues? (do not delete)