Models for AWS Lambda Event Types
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 195
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Based on #48 ,
I'm working on the following events
- APIGatewayCustomAuthorizerEvent
- AppSyncLambdaAuthorizerEvent
- AppSyncLambdaAuthorizerEventResponse
- KinesisAnalyticsFirehoseInputPreprocessingEvent
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #48 and the repository’s existing event-model conventions. Define the scope around APIGatewayCustomAuthorizerEvent, AppSyncLambdaAuthorizerEvent, AppSyncLambdaAuthorizerEventResponse, and KinesisAnalyticsFirehoseInputPreprocessingEvent; done means models for all four event types are covered consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, scala
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100