refactor!: generate per/service base exception types #270
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:
closes #233
Description of changes:
S3Exception
). Previously all exceptions inherited directly fromAwsServiceException/ServiceException
)sdkId
to respect words that are already pascal case.ApiGatewayManagementHub
instead ofApigatewaymanagementhub
for instance (not a real example necessarily). This wasn't strictly necessary but it seemed better to get this in now than later. The base exception types also inherit this naming scheme so we ended up with exceptions likeDynamodbException
orElasticacheException
instead ofDynamoDbException
/ElastiCacheException
etc.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.