feat(core): Allow fetch exchange to handle subscriptions #3106
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.
Summary
This is a proposal which allows the
fetchExchange
to handle subscriptions.This has been submitted to validate the following two assumptions:
OperationContext.fetchSubscriptions
&ClientOptions.fetchSubscriptions
may or may not be a good ideagraphql-yoga
will be able to handle subscriptions viatext/event-stream
/multipart/mixed
response streamsIf these two assumptions are fine, we can go ahead and merge this, I reckon.
Set of changes
OperationContext.fetchSubscriptions
&ClientOptions.fetchSubscriptions
fetchExchange
to handle subscriptions when enabledAccept
header when a subscription is sent