remove subscriptions from allowed POST operations #166
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 executing a subscription operation a client expects multiple results which can best be expressed as a stream, while the incremental delivery RFC could be misused for describing how a stream of subscription events can be delivered to clients, it is clearly not the correct fit, as multipart requests are intended to be short-lived, while subscriptions could stay active for longer periods of time. Until alternative directions such as SSE events (as supported via graphql-helix and graphql-sse) are explored it might make sense to completely remove
subscriptions
from the list of allowed operations that can be executed viaPOST
.