-
Notifications
You must be signed in to change notification settings - Fork 113
Fixes AWS Event namespace problems #203
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
Conversation
1c36e24
to
9267050
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems fine, but maybe still conflicting without some sort of "Lambda" prefix or namespace?
@swift-server-bot test this please |
9267050
to
f26d701
Compare
@fabianfett is this read to merge? |
@tomerd Yes! |
lets port this over to https://github.com/swift-server/swift-aws-lambda-events once after #216 is merged |
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
Will be fixed in the new events repo: swift-server/swift-aws-lambda-events#2 |
Fixes #119.