-
Notifications
You must be signed in to change notification settings - Fork 934
Update test 'bloom filter should correctly encode special unicode characters' in query.test.ts #7413
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
Update test 'bloom filter should correctly encode special unicode characters' in query.test.ts #7413
Conversation
…ment paths with complex Unicode characters, rather than indirectly testing it via the QuerySnapshot.
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected Products
Test Logs |
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
Modify the test
'bloom filter should correctly encode special unicode characters'
inquery.test.ts
, that was added by the recent PR #7412, to directly check the bloom filter for containing the document paths with complex Unicode characters. Previously, it was indirectly checking this via the other properties of the existence filter. As a result, the "retry" logic was removed, since it doesn't matter if there is a false positive.To add the ability to directly interrogate the bloom filter, the testing hooks needed to be augments to expose the "mightContain" method of
BloomFilter
.This PR is ported to the Android SDK in firebase/firebase-android-sdk#5145 and to the iOS SDK in firebase/firebase-ios-sdk#11679.