fix: browser fetch can support streaming request bodies #840
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.
This is a bug fix related to client-streaming requests.
Invoking a
MethodKind.ClientStreaming
method using aconnect
orgrpc-web
transport immediately throws the error "The fetch API does not support streaming request bodies."This, however, appears to be a dated catch. Streaming as a request body is supported by most modern browsers using the default
fetch
.This PR does a very light feature check to ensure backwards compatibility instead of checking against the method's kind.