[RFC] Drop event label from handle methods in LambdaHandlers #225
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.
Drop event label from handle methods in LambdaHandlers protocols
Motivation:
In Lambda functions user's handle events from different sources. Those events can be
S3Event
s, but alsoAPIGatewayRequest
s. Let's look at a Lambda, that integrates with APIGateway.The argument in the
handle
method is labeledevent
even though, in this caserequest
would be clearly a better name. The user could userequest
as a parameter name by explicitly specifying the parameter name:However
event request
is not easy to read and the parameter name overwrite is not the most known swift feature. For this reason I would advice against this option.For this reason I propose dropping the argument label and specifying a parameter name
event
to guide users. New function signature:This would allow users to write lambdas, that integrate with APIGateway as such:
Modifications:
event
label in thehandle
LambdaHandler protocol methodsEventLoopHandler
protocol toEvent
andOutput
(fromIn
andOut
)Result:
A cleaner, more flexible API.