-
Notifications
You must be signed in to change notification settings - Fork 893
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
Fix docs unnecessarily undergo limbo resolution while resuming query bug #7740
Conversation
🦋 Changeset detectedLatest commit: 2df6a61 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
looks good. I think it'd be better to add spec tests rather than modify the existing one. because the old test and the new exercise different series of events
Correct me if I am wrong @dconeybe. The existing one is missing a ".watchCurrent" when resuming a query, adding it on corrects the behaviour, which by the way checks the bug fix. I will add a new spec test dedicated for this bug fix. |
I agree with @milaGGL. The fact that the spec tests were missing the |
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 the fix! Nice job finding the root cause and an elegant solution. Technically, it all LGTM. My comments are merely nitpicks about style and some minor tweaks to improve readability.
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.
Looks great! Please add a changeset so there will be a release notes entry for this fix. Make sure to word it in such a way that a customer who is unfamiliar with implementation details like "limbo resolution" will have some idea of what was fixed.
While resuming a query and there is an existence filter mismatch detected, SDK updated the limbo docs without waiting for a full re-query result.
updateLimboDocuments
in applyChanges tolimboResolutionEnabled
for better semantic meaningPorted to android in firebase/firebase-android-sdk#5506 and ios in firebase/firebase-ios-sdk#12044.