Convert date fields to UTC on the client#410
Open
carlosjdelgado wants to merge 2 commits into
Open
Conversation
Datetime values lost their timezone on the server-side read/write round-trip because the form input has no offset and Vercel runs in UTC: a user in Madrid typing 14:30 ended up stored as 14:30Z. The fix moves the timezone-aware conversion to the browser, where the local offset is known. Edit and view components now treat the stored wall-clock as UTC and shift to local for display; on submit the local input is converted back to a UTC wall-clock. The server keeps doing exactly what it did before (naive parse and format) and, being in UTC, that round-trips correctly. Closes hunvreus#247.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Datetime values lost their timezone on the server-side read/write round-trip because the form input has no offset and Vercel runs in UTC: a user in Madrid typing 14:30 ended up stored as 14:30Z. The fix moves the timezone-aware conversion to the browser, where the local offset is known.
Edit and view components now treat the stored wall-clock as UTC and shift to local for display; on submit the local input is converted back to a UTC wall-clock. The server keeps doing exactly what it did before (naive parse and format) and, being in UTC, that round-trips correctly.
Closes #247.