Better Simulation of Lambda Input and Output #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The actual parameter used to send input to the lambda and get output from said lambda is simply a string value called the
Payload. Therefore, the only way for the AWS SDK to send objects to the lambda and get object from said lambda is through JSON. However, before this PR, lambda-tester was passing these objects nakedly (since all parties are just JavaScript), which caused subtle deviations of behaviour from actually invoking an AWS lambda.This PR fixes this by simulating this serialization process in both input and output. Tests have been modified and added to enforce this behaviour. The existing code style should be preserved.