-
Notifications
You must be signed in to change notification settings - Fork 932
Firestore: query.test.ts: improve the test that resumes a query with existence filter to actually validate the existence filter. #7149
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
Conversation
…existence filter to actually validate the existence filter. This builds upon the test added in #7134
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1This report is too large (567,931 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
… existence filter to actually validate the existence filter. This is a port of firebase/firebase-js-sdk#7149, and builds upon the test added in #4799.
… existence filter to actually validate the existence filter. This is a port of firebase/firebase-js-sdk#7149, and builds upon the test added in #4799.
… existence filter to actually validate the existence filter. This is a port of firebase/firebase-js-sdk#7149, and builds upon the test added in #4799.
This PR improves the test 'resuming a query should use existence filter to detect deletes' in query.test.ts, which was added by the previous PR #7134, to also validate that the existence filter sent from Watch was correct. This was achieved by adding some test-only "hooks" into the SDK's internals that enable the test to "listen" for existence filter mismatches.
Ported to the Android SDK in firebase/firebase-android-sdk#4813
Ported to the iOS SDK in firebase/firebase-ios-sdk#11209