generate util functions to consume response stream #571
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.
Issue #, if available:
Generated change PR: aws/aws-sdk-js-v3#3795
Description of changes:
Now if the deserialized object has streaming blob member(SSDK's input or SDK's output), customers can tranform the stream into string by
Or get the binary data by:
Or transform to runtime-agnostic WebStream by:
The output stream payload's interface is still assignable to the stream payload shape in the input, so this will work:
At the same time, the payload stream is still an instance of the runtime-specific stream implementation, i.e. Stream.Readable in Node.js, ReadableStream in browsers and Blob in React Native. So the code like below will still work:
For SSDK, nothing changed other than operation input shape containing streaming blob member will more strict, for example:
It should be OK as the type exposed to SSDK customers are more strict.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.