fix(Google Calendar node): Correctly set dtstart for recurrence rules in addNextOccurrence function #12266
+62
−1
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
…ccurrence function
…ious recurrence scenarios
marcelreschke
changed the title
|
|
n8n-assistant
bot
added
community
|
Hey @marcelreschke, Thanks for the PR, We have created "GHC-605" as the internal reference to get this reviewed. One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team. |
marcelreschke
changed the title
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.
Summary
Fixes #12262 issue in the Google Calendar node, where the
nextOccurrencefield was not preserving the original event's time when calculating recurring events. The changes include:addNextOccurrencefunction by initializing RRule with properdtstartoptionIt ensures the next occurrence maintains the same time as the original event
Related Linear tickets, GitHub issues, and Community forum posts
Fixes #12262
Review / Merge checklist
release/backport