Add Timestamp support #143
Open
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
This has been the default for Firebase for a while now.
|
This change includes all work from #135. |
Previously, when a document have a reference to another document, we ended up in an infinite loop. This is now prevented by only follow plain objects. This logic makes it easier to reason about the call chain too.
Previous behavior for Server Timestamp was to return UNIX timestamp. This is the correct bahviour still for the client firebase.database library. This change restores this.
Internally date is now stored as Date until returned, where it is converted to Timestamp. This fixes orderBy.
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.
This is a breaking change, which follows upstream breaking change on returning Timestamp instead of Date.
References: