fabianfett / swift-lambda-runtime Goto Github PK

https://github.com/aws/aws-lambda-go/blob/master/events/firehose.go

on macOS

Test Case '-[LambdaRuntimeTests.SNSTests testSimpleEventFromJSON]' started.
/Users/johannes/extsrc/swift-lambda-runtime/Tests/LambdaRuntimeTests/Events/SNSTests.swift:80: error: -[LambdaRuntimeTests.SNSTests testSimpleEventFromJSON] : failed - Unexpected error: dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "Records", intValue: nil), _JSONKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "Sns", intValue: nil), CodingKeys(stringValue: "Timestamp", intValue: nil)], debugDescription: "Expected date to be in format `Optional(\"yyyy-MM-dd\\\'T\\\'HH:mm:ss.SSSZ\")`, but `Optional(\"yyyy-MM-dd\\\'T\\\'HH:mm:ss.SSSZ\") does not forfill format`", underlyingError: nil))
Test Case '-[LambdaRuntimeTests.SNSTests testSimpleEventFromJSON]' failed (0.001 seconds).

Log label: "aws.lambda.swift.request-logger"

https://github.com/aws/aws-lambda-go/blob/master/events/s3.go

https://github.com/aws/aws-lambda-go/blob/master/events/dynamodb.go

https://github.com/aws/aws-lambda-go/blob/master/events/kinesis.go

I guess a GitHub Action should be build that automatically checks, if there is a new Swift version. If a new version is available, a new commit should be made in a separate repository that also gets a git tag. Then we can upload the Layer binary to the release tag. That way we always have the newest version. No manual work required.

The Go implementation says something different than the official 1-click IoT documentation:
https://docs.aws.amazon.com/iot-1-click/latest/developerguide/1click-programming.html#1click-events

Go implementation:
https://github.com/aws/aws-lambda-go/blob/master/events/iot_button.go

Go test event:
https://github.com/aws/aws-lambda-go/blob/master/events/testdata/iot-button-event.json

Does anyone have an IoT-Button so that we can generate a real event?

We could think about splitting the events into an extra package LambdaEvents within this repository. With this other LambdaRuntimes could use the events as well, without having to import LambdaRuntime. What do you think?

• implement via protocol BodyDecodable
• use @available syntax to guide developers to new implementation.