-
Notifications
You must be signed in to change notification settings - Fork 196
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
Avoid making FsBuilder
aware of http-body version at interface level
#3101
Avoid making FsBuilder
aware of http-body version at interface level
#3101
Conversation
A new generated diff is ready to view.
A new doc preview is ready to view. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! lgtm
6f910d9
to
66dc4b0
Compare
A new generated diff is ready to view.
A new doc preview is ready to view. |
https://github.com/awslabs/smithy-rs into ysaito/do-not-make-fs-builder-http-body-version-aware
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
Motivation and Context
Follow up on #3088
Description
This PR reverts
ByteStream::read_with_body_0_4_from
,ByteStream::from_path_body_0_4
, andByteStream::from_file_body_0_4
to the old names since from a customers' point of view,FsBuilder
should not mention anything about anhttp-body
version at the API level.FsBuilder
is currently an opt-in feature (withrt-tokio
enabled) and we make it tied tohttp-body-0-4-x
by requiringrt-tokio
including a dependency onhttp-body
version 0.4.x.Testing
Relied on the existing tests in CI
Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.