Split out SimpleEmailEventsReceiptAction into different action types #496
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.
Description of changes:
We were trying to use this library to allow us to have a lambda handle emails being received with an S3 action. However, the library as was only supports Lambda. So we're currently using dynamic to get around this limitation, but I'd rather be type safe.
So, what I've done, is split the SimpleEmailReceiptAction into an interface and 2 different action types. This type can then be passed in as a
<T>
at any level of the nested classes, and will resolve properly. Unit tests confirm.It would help us be type safe were this request to be confirmed.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.