Ignore TZID when parsing time with UTC indicator - #11250
Open
lakshay-2411 wants to merge 1 commit into
Open
Conversation
Contributor
|
Thank you! |
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
2 participants
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.
Fixes #11248
parseTime threw a ParserError when a date-time value had both a TZID parameter and a Z (UTC) suffix, which broke entire calendar subscriptions for non-compliant feeds like F1TV (DTSTART;TZID=Etc/GMT:20260725T121500Z).Per RFC 5545 the Z form is authoritatively UTC, so the TZID is now ignored (with a console warning), matching the zone precedence already used in parseRecurrenceId. The edge-case test asserting the throw was updated to assert the new behavior; genuinely invalid timezones still throw (#11022 behavior preserved).