Catchup with current version of aws-lambda-go #39
Conversation
|
Thank you for the patch! The test failure looks legit? |
|
It looks like aws/aws-lambda-go@b4388e4#diff-862417b9e7c3720bcb3263cd873b09892d787823b6f9a0f453e42824c5a4d4b6 might have introduced the breaking change, via this PR: |
|
Filed aws/aws-lambda-go#390. |
|
You'll also want to update https://github.com/LegNeato/aws-lambda-events/blob/master/aws_lambda_events_codegen/src/main.rs#L143 as the test event has been renamed in the latest go sdk (in aws/aws-lambda-go@ee817dd) |
|
Great. Looks like there is a PR to fix the issue on the go side. Once that lands can you regenerate this to get the tests to pass? After I'll cut a release. Thank you again for the PR! 🍻 |
|
@LegNeato aws/aws-lambda-go#392 just got merged, so I have now regenerated the code. Tests seem to pass as well! |
|
Awesome, thank you! I'll do a crates.io release tomorrow. |
|
This has now been released to crates.io, sorry for the delay! 🍻 |
2 participants
This should also fix #36, and https://github.com/lamedh-dev/aws-lambda-rust-runtime/issues/25.