fix: rely on IANA Vancouver timezone#1666
Conversation
|
Temporary Url for review: https://strr-hosts-dev--pr-1666-m0tu559t.web.app |
cf4fb81 to
e821a5b
Compare
|
Temporary Url for review: https://strr-hosts-dev--pr-1666-m0tu559t.web.app |
|
@Jacky-Pham can these changes be applied right away or is there a scheduled date we need to target? |
There should be no significant impact to users and we need to make sure this is working as soon as possible as per SRE. The effective transition date was already March 8, 2026 so we need these in sooner rather then later |
dimak1
left a comment
There was a problem hiding this comment.
Added a few comments. Also, please bump up the versions in apps that were changed. Thanks!
|
|
||
| const HISTORICAL_PACIFIC_TIME_ZONE = 'America/Vancouver' | ||
| const PACIFIC_TIME_ZONE = 'UTC-7' | ||
| const PACIFIC_TIME_TRANSITION_UTC = DateTime.fromISO('2026-03-08T10:00:00Z', { zone: 'UTC' }) |
There was a problem hiding this comment.
We should have some comment regarding this hardcoded date.
| const PACIFIC_TIME_ZONE = 'UTC-7' | ||
| const PACIFIC_TIME_TRANSITION_UTC = DateTime.fromISO('2026-03-08T10:00:00Z', { zone: 'UTC' }) | ||
|
|
||
| function asPacificTime (date: DateTime): DateTime { |
There was a problem hiding this comment.
Do we need to define exact same functions here in host app, when base already have it? There are quite some duplication between here and date utils in base-web.
e821a5b to
73b2db2
Compare
73b2db2 to
8afbc6d
Compare
|
Updated this after the timezone discussion:
|
dimak1
left a comment
There was a problem hiding this comment.
Looks cleaner now, approve
|



Summary
America/Vancouvertimezone for legislative Pacific Time handlingDateUtilso API paths use the same timezone helperAmerica/VancouverTesting
Closes #1600