fix: SQS receive message middleware properly calls next() once #1680
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:
#1394
SQS middleware was calling next({}) in https://github.com/alexforsyth/aws-sdk-js-v3/blob/58e4d4a4d20acfa8e123b87532baeb8b836960e3/packages/middleware-sdk-sqs/src/receive-message.ts#L30 and later on in the return. Fixed so that the return correctly gives back the result of processing in the queue
Description of changes:
SQS middleware no longer calls next({...}) twice and now correctly returns messages from the queue.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.