-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve create() with WriteResult #29
Conversation
…content must be served
This has been the default for Firebase for a while now.
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.
Previously, gulp-shell did not properly signal completion, resulting in errors with Gulp 4. Fixed now.
# Conflicts: # src/storage-bucket.js # src/storage.js
Fix: Add Boolean support to Query equalTo
Pass a `User` into the setup instead of a plain object. Also, fix one typo in a test name.
Firebase SDK [Version 4.0.0](https://firebase.google.com/support/release-notes/js#version_500_-_may_8_2018) changed the behavior of `onAuthStateChanged` and added a new event handler called `onIdTokenChanged`. This patch mocks that change. onIdTokenChanged now implements the former behavior of onAuthStateChanged. onAuthStateChanged now signals only when the actual user changes, not when a new ID token is set for the same user.
Change NPM URLs to new repo
Remove two unused imports
# Conflicts: # CHANGELOG.md
# Conflicts: # package-lock.json # src/firestore-document-snapshot.js # src/firestore-document.js # src/firestore-query.js # src/utils.js # test/unit/firestore-collection.js # test/unit/utils.js
…mock into create-write-result
I'm realizing now that this PR doesn't make the problem any worse than it already is. We have an issue where if you call You're right that none of that has anything to do with this PR, so I'm going to merge it. Cheers. |
Thank you 🙏 |
Reopening the original PR here.