Repository navigation
Fix ambiguous timestamping - #54
Merged
Merged
Conversation
patricklatimer
approved these changes
Jun 2, 2026
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
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.
Updates
This PR enforces all server replies to return a timestamp. Beforehand, it was optional as to whether you wanted to send the timestamp from the server, but the client needed to know if the timestamp was sent to be able to retrieve the data correctly. Because there was no way to know this, this pr just makes it so the timestamp is always sent with the data.
@micahwoodard I will make the needed adjustments to prototome-web-ui!
Merge Checklist