ParseLiveQuery controller should wrap all subscription events #405
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM! Thanks for the PR, and sorry for the late review! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When you call
subscribe()on a query (which goes through the ParseLiveQuery controller), the resulting subscription does not currently receivecloseorerrorevents for the underlying connection. This was occurring because the LiveQueryController is wrapping the underlying subscriptions, and was not forwarding thecloseorerrorevents.This pull request correctly wraps these two event types so that subscriptions receive all the event notifications they are supposed to, and introduces a new test case to check that all subscription events are forwarded correctly.