fix: null deserialization of stageVariables for sam local #366
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: #365
Description of changes:
Add support for deserializing API Gateway v2 payloads when
stageVariables
is set to null.AWS SAM local sends a payload that contains a null value for
stageVariables
, which causes the deserialization into alambda_http::request::LambdaRequest
to fail. This makes this field deserializable using thenullable_default
function to handle that edge case.Open question: should we also make this change to all fields that deserializes into a
StrMap
?By submitting this pull request