-
Notifications
You must be signed in to change notification settings - Fork 154
Feature request: implement makeBatchHandler
Middy middleware
#1608
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
Comments
With the current implementation of the Batch Processing utility, processing a batch of records sent to a Lambda handler requires one line (excluding formatting): export const handler = async (
event: SQSEvent,
context: Context
): Promise<SQSBatchResponse> => {
return await asyncProcessPartialResponse(event, recordHandler, processor, {
context,
});
}; At the moment we are unsure about the value added by a Middy middleware besides syntactic sugar for those users who like using middlewares as a pattern. For this reason we are excluding this feature from the base version of the utility and will leave the issue open so that customers can express their interest. If there's enough demand we will implement the middleware before the utility reaches General Availability. |
Due to the lack of traction on this issue in the last 6+ months, I'm gonna go ahead and close it. If you are interested in this feature, please open a new feature request describing your use case and we'll be happy to reconsider. |
This issue is now closed. Please be mindful that future comments are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so. |
Use Case
Customers who use Middy middlewares might want to use the Batch Processing utility as a Middy middleware.
Solution/User Experience
Refer to example shown in the RFC #1082, section 3.2
Acceptance criteria
The text was updated successfully, but these errors were encountered: