Refactor smithy_types::Error to be more flexible (Breaking Change) #426
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: #422
Description of changes:
S3 (and probably other) services have errors with an additional set of metadata that must be recorded. This diff does a few things:
This will make it straightforward to add per-service customizations to record additional error metadata. Services will define their own extension traits to add strongly-typed property bag accessors.
Breaking Change: This is a breaking change because fields on error that were public are now private.
Fix: Change code that accessed fields directly to use accessors:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.