Automatic Daylight Saving and Date Adjustments #21
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build
) was run locally and any changes were pushednpm run lint
) has passed locally and any fixes were made for failuresPull request type
Please check the type of change your PR introduces:
What is the current behavior?
The
RegionTimeZoneMapping
variable is manually updated some time after Daylight Saving occurs for NA and EU servers, which unfortunately occurs on different Sundays (2nd/1st Sundays of March/Nov respectively for NA, and last Sundays of March and Oct for EU). South American servers are most likely not affected by DST.Users looking at events happening the following day after the page loads will always initially be told that events are happening "in 23 hours". This is because time is calculated relative to when the user initially accessed the page.
The automatic date changer changes dates when the local current time hits midnight. Users living in time zones that do not line up with the selected server's time zone may experience unexpected behavior when either the local or server date changes.
Note that these issues can currently be resolved manually by clicking on the date button, or by refreshing the page
What is the new behavior?
Improved automation
Does this introduce a breaking change?