WIP: Cookbook example showing how to handle icalendar time zones #2894
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 is an example of how a ZonedDateTime object with a custom time zone could work, if TimeZone objects are removed. (#2853)
This shows integration with ical.js. It's a ZonedDateTime-wrapper object that internally maintains a real
Temporal.ZonedDateTime
object, but it takes anICAL.Timezone
instead of aTemporal.TimeZone
. If theICAL.Timezone
object has the ID of an IANA time zone, we delegate everything to the realTemporal.ZonedDateTime
and use the host's time zone database. If the ID is not an IANA ID, we fall back to theICAL.Timezone
'sVTIMEZONE
data.Draft; still needs test data with which to make sure everything works, and a cookbook page.