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.
NOTE: This change was added because test cases like this were failing:
I correctly received an event on 11/04/2019, but since 1 month was added to this start date, the next month started looking for "first monday" on 12/04/2019 and returned 12/09/2019 when it should have returned 12/02/2019.
TEST CASE EXAMPLE:
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20191104T090000
DTEND;TZID=America/Los_Angeles:20191104T100000
RRULE:FREQ=MONTHLY;BYDAY=1MO
DTSTAMP:20191023T175925Z
UID:6uvrlpou5dsso6hnng6p65es41@google.com
CREATED:20191021T154144Z
DESCRIPTION:
LAST-MODIFIED:20191021T220941Z
LOCATION:
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Test Monthly First Monday
TRANSP:OPAQUE
END:VEVENT
Attached is a test file I used to verify my changes in multiple scenarios.
multiRecurrExamples.ics.txt