Repository navigation
Accept UTC starts in timezone-aware RRULE schedules - #28
Merged
Merged
Conversation
This file contains hidden or 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
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.
An
RruleSchedulewith a UTC start such asDTSTART=20260501T090000Zthrows when a timezone is also configured. The formatter addsTZIDto the already-UTC value, producing an invalid combination that php-rrule rejects.Only add
TZIDto local start values. Explicit UTC starts keep their original meaning, including after the schedule is reloaded or its timezone changes.Validated with the full Pest suite (149 tests) and Pint.
Fixes #22.