Move aws_smithy_http::result into aws-smithy-types
#3092
Assignees
Comments
ysaito1001
changed the title
ConnectorError into a future-stable crateaws_smithy_http::result into aws-smithy-types
This was referenced Oct 24, 2023
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 27, 2023
…runtime-api` (#3103) ## Motivation and Context Implements #3092 ## Description This PR moves the `connection` and `result` modules from `aws-smithy-http` to `aws_smithy_runtime_api`. `SdkError` is primarily used within the context of the orchestrator, hence `aws_smithy_runtime_api` instead of `aws-smithy-types`. Like the previous sibling PRs, type aliases for affected pub items are left in `aws_smithy_http` for backwards compatibility. However, due to lack of trait aliases, a trait `CreateUnhandledError` needs to be consumed from `aws_smithy_runtime_api`. This PR also updates existing places that consumed those moved types so they now depend on `aws-smithy-runtime-api` to do so. ## Testing Relied on the existing tests, which ensured no deprecated warnings of using moved types from the old place were issued. ## 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._
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: