-
Notifications
You must be signed in to change notification settings - Fork 33
feat: batch typed decorator #1034
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
base: develop
Are you sure you want to change the base?
Conversation
- Updated BatchProcessorAttribute to allow configuration of typed handlers for DynamoDB, Kinesis, and SQS events. - Introduced CreateTypedBatchProcessingAspectHandler method to handle typed batch processing. - Added validation for typed handler configurations. - Implemented singleton instances for TypedDynamoDbStreamBatchProcessor, TypedKinesisEventBatchProcessor, and TypedSqsBatchProcessor. - Refactored constructors to accept Powertools configurations and default services for typed processors.
the documentation file was wrongly formated fixed, so looks like the whole file changed but in reality just one line |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #1034 +/- ##
===========================================
+ Coverage 78.12% 78.25% +0.13%
===========================================
Files 298 299 +1
Lines 12003 12222 +219
Branches 1441 1471 +30
===========================================
+ Hits 9377 9564 +187
- Misses 2163 2189 +26
- Partials 463 469 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Issue number: closes #1033
Summary
Changes
Full support for TypedRecordHandler and TypedRecordHandlerWithContext
User experience
Checklist
Please leave checklist items unchecked if they do not apply to your change.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.