Skip to content

fix parsing non-readable stream #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 6, 2020

Conversation

srchase
Copy link
Contributor

@srchase srchase commented Jan 3, 2020

Use existing output body on structures instead of using parseBody to collect the stream.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@srchase srchase requested a review from kstich January 3, 2020 23:07
Copy link
Contributor

@kstich kstich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Taking this as a fix while #66 is worked on.

@srchase srchase merged commit eff63bf into smithy-lang:master Jan 6, 2020
@srchase srchase deleted the error-stream-parsing branch January 6, 2020 18:56
trivikr added a commit to trivikr/aws-sdk-js-v3 that referenced this pull request Jan 6, 2020
srchase pushed a commit to srchase/smithy-typescript that referenced this pull request Mar 17, 2023
srchase pushed a commit that referenced this pull request Mar 23, 2023
* Adds Command Generator
* Adds CodeCommit node package
srchase pushed a commit that referenced this pull request Jun 16, 2023
* Adds Command Generator
* Adds CodeCommit node package
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants