-
Notifications
You must be signed in to change notification settings - Fork 190
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
Move aws_smithy_http::operation::error::BuildError
into aws-smithy-types
#3032
Move aws_smithy_http::operation::error::BuildError
into aws-smithy-types
#3032
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.
@jdisanti do you think this makes more sense in aws-smithy-runtime-api
? I guess we need to define a litmus test of what goes where.
Yeah, that distinction is blurry to me. For things like |
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. |
This commit addresses #3032 (comment)
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. |
Co-authored-by: John DiSanti <jdisanti@amazon.com>
This commit addresses #3032 (comment)
A new generated diff is ready to view.
A new doc preview is ready to view. |
…3070) ## Motivation and Context Completes #3054 (a follow-up on #3032) ## Description #3032 moved `BuildError` from `aws_smithy_http::operation::error` to `aws_smithy_types::error::operation`. That PR also left "breadcrumbs", so that customers could still consume `BuldError` from `aws_smithy_http` after the move. This PR turns breadcrumbs into deprecation messages (via `#[deprecated(...)]`) and updates existing places that used to use moved types from `aws_smithy_http` to `aws_smithy_types`. ## Testing Relied on tests in CI. ## Checklist - [x] I have updated `CHANGELOG.next.toml` if I made changes to the smithy-rs codegen or runtime crates ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._ --------- Co-authored-by: Russell Cohen <rcoh@amazon.com>
Motivation and Context
Takes care of the first part of #3054 (the remaining part is denoted as
TODO(runtimeCratesVersioningCleanup)
and until that's done the issue will not be closed).Description
This PR moves from
aws-smithy-http::operation::error::{BuildError, SerializationError}
toaws-smithy-types::error::operation::{BuildError, SerializationError}
.Within the origin crate, we leave "breadcrumbs" (i.e. reexports) for existing customers of the items above so they are not broken by the move. The breadcrumps will be removed by the part two of the issue.
As part of the move,
aws_smithy_http::endpoint::EndpointPrefix::new
now returns itscrate::endpoint::error::InvalidEndpointError
instead ofcrate::operation::error::BuildError
for two reasons:BuildError
is now in a stable crate and for anInvalidUri
variant to be created, it needed to take ahttp::uri::InvalidUri
from a unstable crate, which we cannot expose in public API.Testing
Relied on the 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.