Fix Trips Page Timezone Issue #119
Merged
Conversation
This file contains 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
…C time to fix issue #89.
…ing from trip.test.js to this file.
keiffer01
approved these changes
Jul 30, 2020
anan-ya-y
approved these changes
Aug 3, 2020
HiramSilvey
approved these changes
Aug 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is a quick description of the change?
Fix #89 by ensuring that all JS Date objects use UTC.
This ensures that no matter where the user is located when updating or viewing the trips, the start and end date of the trips will remain the same from the last update.
Is this fixing an issue?
Fixes #89: see above.
Are there more details that are relevant?
Moves getDateRangeString into
time.js.Check lists (check
xin[ ]of list items)Any additional comments?