Properties of HTTPResponses are now var #176
Merged
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.
Properties of HTTPResponse types should be
var
notlet
Motivation:
When creating responses in Lambda developers might want to create the response in multiple steps changing and adding properties. As of now this is not possible since all HTTPResponse types only have
let
properties. If a developer wants to mark a response as immutable they have still the option to mark the complete response aslet
.Modifications:
APIGateway.Response
,APIGateway.V2.Response
,ALB.TargetGroupResponse
) are nowvar
iableAPIGateway.V2.Response
. See example/documentation at the very endResult:
Developers have an easier job creating responses. 🥳