-
Notifications
You must be signed in to change notification settings - Fork 885
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
Backport updates from Android (multiple changes) #1912
Conversation
…tId, backport documentation updates from Android
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for back-porting everything! You can now call yourself a true Firestore SDK developer. 😛 This mostly looks great, but I found a potential issue (though maybe I'm confused since I thought tests should have caught it 🤔 )...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with (optional) nit. Please back-back-port the new test to Android. 😁
@mikelehen I just realized that the current implementation of This means that Gil's refactor of filter PR needs to go in first, or else I'll be doing the logic twice. I'll submit this PR for now, and back-back-backport(?) the integration test once the Android refactor of Filter is done to include |
👍 |
Backporting changes from Android IN queries:
null
andNaN
and reorganize tests to match Android SDKclearPersistence()
to include Rachel's editsThis change introduces
KeyFieldInFilter
, which stacks on top of @wilhuff's refactor (#1894). This will be ported to Android when he refactors the Android client.TODO: After this change goes in, I will update the error messages inside
parseDocumentIdValue()
to match the Android SDK, since those error messages are more generally applicable to both IN queries and KeyFieldFilter queries.