Skip to content

Fix event namespacing problems #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 19, 2021

Conversation

fabianfett
Copy link
Member

Motivation

We have potential name clashes with existing AWS libraries, if we namespace our events under the service name. For example S3.Event. This problem has been documented here: swift-server/swift-aws-lambda-runtime#119

Changes

This PR picks up the fix, that was initially intended to land in the runtime repo directly: swift-server/swift-aws-lambda-runtime#203

Result:

No more namespace issues with AWS libraries.

We have potential name clashes with existing AWS libraries, if we namespace our events under the service name. For example `S3.Event`. This problem has been documented here: swift-server/swift-aws-lambda-runtime#119

### Changes

This PR picks up the fix, that was initially intended to land in the runtime repo directly: swift-server/swift-aws-lambda-runtime#203
@tomerd
Copy link
Contributor

tomerd commented Aug 19, 2021

@fabianfett looks good but sample needs to be fixed?

@fabianfett
Copy link
Member Author

@tomerd Sample pushed, but requires 5.5...

@tomerd
Copy link
Contributor

tomerd commented Aug 19, 2021

@swift-server-bot test this please

@fabianfett fabianfett merged commit 2bffdda into swift-server:main Aug 19, 2021
@fabianfett fabianfett deleted the ff-event-renamings branch August 19, 2021 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants