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.

Sign up for GitHub

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

Jump to bottom

message field is None when errors rename messages #372

Closed
rcoh opened this issue May 13, 2021 · 0 comments · Fixed by #374
Closed

message field is None when errors rename messages #372

rcoh opened this issue May 13, 2021 · 0 comments · Fixed by #374
Labels
bug Something isn't working papercut tiny bugs that make the SDK harder to use

Comments

@rcoh
Copy link
Collaborator

rcoh commented May 13, 2021

Eg. lambda::InvokeError. Because the message field can't be parsed using the "normal" generic parser invoking .message() on the top level error confusingly returns None
@rcoh rcoh added bug Something isn't working papercut tiny bugs that make the SDK harder to use labels May 13, 2021
@rcoh rcoh mentioned this issue May 13, 2021
Merged
@rcoh rcoh closed this as completed in #374 May 13, 2021
@rcoh rcoh mentioned this issue Jun 30, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working papercut tiny bugs that make the SDK harder to use
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Gracefully handle alternate error message fields smithy-lang/smithy-rs
1 participant
@rcoh