fix(#429): missing recurrences for certain timezones #435
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.
This fixes an issue pointed out in #429 where some recurring events will not display. Here is a minimal example you can use to reproduce the problem:
The issue is that the recurrence gets created, and then
convertEventTimeZoneis called on the event, which pushes the event to the next day. Because the event is now on the next day, thefilterTodayEventsfunction ignores it, and the event is never displayed. This fixes the issue by looking for recurrences in the range of [today-1, today+1] instead of [today, today+1]. If the timezoned event then moves into the next day, it is still included on the calendar.