-
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
Re-export aws_smithy_types::date_time::Format
in service client crates
#2534
Conversation
This commit adds two more client re-exports that were not included in smithy-rs#2437: - `aws_smithy_http::byte_stream::Length` - `aws_smithy_types::date_time::Format`
A new generated diff is ready to view.
A new doc preview is ready to view. |
Should we re-export these under |
This commit removes re-export of `aws_smithy_http::byte_stream::Length` for now as it is a feature-gated type, which requires further consideration.
A new generated diff is ready to view.
A new doc preview is ready to view. |
aws_smithy_types::date_time::Format
in service client crates
Yes, and as discussed off-line, we'll re-export them by prefixing. So |
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. |
…tes (#2534) * Add more client crate re-exports This commit adds two more client re-exports that were not included in smithy-rs#2437: - `aws_smithy_http::byte_stream::Length` - `aws_smithy_types::date_time::Format` * Remove re-export of `aws_smithy_http::byte_stream::Length` This commit removes re-export of `aws_smithy_http::byte_stream::Length` for now as it is a feature-gated type, which requires further consideration. * CHANGELOG.next.toml --------- Co-authored-by: Yuki Saito <awsaito@amazon.com>
…tes (#2534) * Add more client crate re-exports This commit adds two more client re-exports that were not included in smithy-rs#2437: - `aws_smithy_http::byte_stream::Length` - `aws_smithy_types::date_time::Format` * Remove re-export of `aws_smithy_http::byte_stream::Length` This commit removes re-export of `aws_smithy_http::byte_stream::Length` for now as it is a feature-gated type, which requires further consideration. * CHANGELOG.next.toml --------- Co-authored-by: Yuki Saito <awsaito@amazon.com>
…tes (#2534) * Add more client crate re-exports This commit adds two more client re-exports that were not included in smithy-rs#2437: - `aws_smithy_http::byte_stream::Length` - `aws_smithy_types::date_time::Format` * Remove re-export of `aws_smithy_http::byte_stream::Length` This commit removes re-export of `aws_smithy_http::byte_stream::Length` for now as it is a feature-gated type, which requires further consideration. * CHANGELOG.next.toml --------- Co-authored-by: Yuki Saito <awsaito@amazon.com>
Motivation and Context
This small PR is a follow-up on #2437. We re-export
aws_smithy_types::date_time::Format
intoprimitives.rs
(or intotypes.rs
prior to the client crate re-organization).Description
Note if we run
rg aws_smithy_*
inaws-doc-sdk-examples/rust_dev_preview
, we see use statements onaws_smithy_types_convert::date_time::Error
aws_smithy_types_convert::date_time::DateTimeExt
These types are under consideration. They are feature-gated in
aws_smithy_types_convert
and we probably do not want to turn on the cargo feature and re-export them by default across client crates.Testing
Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesCHANGELOG.next.toml
if I made changes to the AWS SDK, generated SDK code, or SDK runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.