Use X-WR-TIMEZONE as calendar tz when available, fallback to UTC #2091
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.
When checking current shifts to trigger slack notifications, a stable value for timezone should be used (to avoid triggering multiple duplicated notifications; using the first
VTIMEZONE
value available may change on refresh, besides being potentially incorrect).Also,
VTIMEZONE
shouldn't be used as the calendar timezone, it just describes a timezone definition which can later be used when specifying a start/end date/datetime ("The parameter MUST be specified on properties with a DATE-TIME value if the DATE-TIME is not either a UTC or a "floating" time.").OTOH, Google uses the non-standard
X-WR-TIMEZONE
field as fallback TZ for date-times without aTZID
. Try to use this when available, otherwise fallback toUTC
.