Skip to content
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

Fix retry config doc comments and remove re-export #1935

Merged
merged 4 commits into from
Nov 4, 2022

Conversation

jdisanti
Copy link
Collaborator

@jdisanti jdisanti commented Nov 2, 2022

Motivation and Context

The doc comments on aws_smithy_client::retry::Config weren't rendering properly, and I'm not sure why this struct was getting re-exported in the SDK's middleware module since it is only really useful in the retry implementation.

Checklist

  • I have updated CHANGELOG.next.toml if I made changes to the AWS SDK, generated SDK code, or SDK 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.

@jdisanti jdisanti requested a review from a team as a code owner November 2, 2022 21:31
@jdisanti jdisanti requested a review from a team as a code owner November 2, 2022 21:33
@jdisanti jdisanti changed the title Fix retry config doc comments and re-export Fix retry config doc comments and remove re-export Nov 2, 2022
@github-actions
Copy link

github-actions bot commented Nov 2, 2022

A new generated diff is ready to view.

A new doc preview is ready to view.

@jdisanti jdisanti enabled auto-merge (squash) November 3, 2022 23:40
@github-actions
Copy link

github-actions bot commented Nov 3, 2022

A new generated diff is ready to view.

A new doc preview is ready to view.

@jdisanti jdisanti merged commit e2e0d93 into main Nov 4, 2022
@jdisanti jdisanti deleted the jdisanti-fix-retry-config branch November 4, 2022 00:09
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.

3 participants