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

Allow <Error> to trigger error handling for S3 #2958

Merged
merged 4 commits into from
Aug 30, 2023
Merged

Conversation

rcoh
Copy link
Collaborator

@rcoh rcoh commented Aug 29, 2023

Motivation and Context

Description

Add a customization for S3 so that if <Error> is the root element, we trigger the error parsing flow

Testing

  • Added an integration test

Checklist

  • I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates
  • 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.

@rcoh rcoh requested review from a team as code owners August 29, 2023 17:29
section.body?.also { body ->
rustTemplate(
"""
if matches!(dbg!(#{errors}::body_is_error(&$body)), Ok(true)) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if matches!(dbg!(#{errors}::body_is_error(&$body)), Ok(true)) {
if matches!(#{errors}::body_is_error(&$body), Ok(true)) {

@github-actions
Copy link

A new generated diff is ready to view.

A new doc preview is ready to view.

@github-actions
Copy link

A new generated diff is ready to view.

A new doc preview is ready to view.

@github-actions
Copy link

A new generated diff is ready to view.

A new doc preview is ready to view.

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.

None yet

2 participants