Call this.currentObservable.tearDownQuery more consistently. #7259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #7205, per my comment #7254 (comment).
Instead of tearing down
queryData.currentObservable
only whenqueryData.getOptions().skip
is true inremoveQuerySubscription
(which was the idea of #7205), I split the tear-down functionality into a separate private method (removeObservable
), which works regardless of theskip
status, and is called everywhereremoveQuerySubscription
is called, except inresubscribeToQuery
, where we specifically want to preservethis.observableQuery
.