Closed DavidSouther closed 1 year ago
This looks suspiciously similar to #365 and #367, which makes me think that either the example is too loose, or the definitions in lambda_http are too strict.
makes me think that either the example is too loose, or the definitions in lambda_http are too strict.
There is no specification about the payloads, so it's hard to tell. Other languages are definitely more forgiving than Rust parsing those examples. Given the payload that you have in the description, it should be easy to add a new test case in the apigw module to validate that those payloads are supported:
Comments on closed issues are hard for the maintainers of this repository to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
In my case, I ran into this data did not match any variant of untagged enum LambdaRequest
error because I was using the apigw_http
feature but fronting my Lambda with an APIG REST API (was originally using a Lambda Function URL). Swapping this feature with apigw_rest
resolved the issue for me.
When invoking a lambda_http service function using the template payload from the Lambda test console, serde fails to deserialize.
Cargo.toml:
bin/upload_err.rs:
example.json:
Runner:
Invoke:
Log: