Preserve the observer associated with an existing topic #37
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 a new request is executed, we need to make sure the observer intially associated with a topic is preserved. currently, on a new request, we disconnect all the clients and then reconnect them and associate them with the latest observer. When a subscription message is received, we then fetchthe observer with:
this.topicObserver.get(topic);
and call
observer.next(parsedMessage);
which will trigger a specific handler configured for that observer (the handler that subscribed to the observer returned by the
execute
function inQueryManager.startGraphQLSubscription
.The change keeps track of the previous value of
topicObserver
and retains the observer associated with an existing topic.