Skip to content

Adding default constructor for S3Event for easier deserialization #63

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 1 commit into from
Nov 14, 2018

Conversation

galbash
Copy link

@galbash galbash commented Nov 8, 2018

Issue #, if available: No issue opened.

Description of changes: Adding a default constructor to the S3Event. The reason for doing this is that it already has another constructor (which gets a list of records), so when working with Jackson we might encounter some issues when trying to deserialize data into this type.
The reason for adding the empty constructor is similar to the one explained here: https://docs.aws.amazon.com/lambda/latest/dg/java-handler-io-type-pojo.html under "note". Also, every other event class has a default constructor.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@galbash galbash force-pushed the s3-event-default-constructor branch from fc97201 to 4d7cc9e Compare November 13, 2018 13:43
@bmoffatt bmoffatt merged commit 9d36c53 into aws:master Nov 14, 2018
maxday pushed a commit that referenced this pull request Jun 28, 2024
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