Skip to content
This repository was archived by the owner on Jul 14, 2020. It is now read-only.

ByteBuffer should be optional in APIGateway #10

Closed
duong-ta opened this issue Dec 19, 2019 · 1 comment
Closed

ByteBuffer should be optional in APIGateway #10

duong-ta opened this issue Dec 19, 2019 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@duong-ta
Copy link

No description provided.

fabianfett added a commit that referenced this issue Dec 19, 2019
@fabianfett fabianfett self-assigned this Dec 19, 2019
@fabianfett fabianfett added this to the 0.2.0 milestone Dec 26, 2019
@fabianfett fabianfett added the bug Something isn't working label Dec 29, 2019
fabianfett added a commit that referenced this issue Dec 31, 2019
This PR changes everything. Sorry. But growing up always comes with a pain.

- New package name: `swift-lambda-runtime`. The library is now called `LambdaRuntime` (#11)
- The Runtime now only has one handler function. This is more in line with the [go sdk](https://github.com/aws/aws-lambda-go). The end user still has the option to specify different handler methods by using the env variable `_HANDLER`
- The runtime is now intended to be used with the [amazonlinux-swift](https://fabianfett.de/amazonlinux-swift) project. That is why the makefile to extract Swift libraries from the Ubuntu Swift Dockerimage has been removed.
- `swift-base64-kit` has been added as a dependency to support future Event types.
- It is possible now to not return a result from the function (#10)
- The synchronous interface has been removed.
- The documentation explains how to create a development image (#9)
- The documentation has been changed to reflect the changes.
@fabianfett
Copy link
Owner

Fixed with #8.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants