-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Serve: JSON Body Handling #95
Comments
I'm having the same problem. This is a quote from the serverless documentation regarding lambda-proxy.
|
Just looked at your change. I think you need to do a little bit more. I think you only want to switch to text parser if the integration type is lambda-proxy. |
Will amend and raise the PR thanks for confirming this and taking a look into it :D |
@jonsharratt @anozaki If you use the serve functionality, it would be great if you could comment in #135 . |
|
Not sure if anyone else if having the same issue but the Lambda Proxy integration functions I have setup when deployed do not parse the JSON and thus the events
body
property requires parsing in my lambda function (e.g. https://github.com/craftship/yith/blob/master/src/user/put.js#L8) when a request is sent withContent-Type
application/json
.In order to replicate the same functionallity when running the
webpack serve
command I had to do the following:master...craftship:use-text-parser
I have not raised a PR yet as wanted to see if I was missing anything obvious / missed something I should test further.
Let me know, thanks for the awesome plugin has really helped our project long!
The text was updated successfully, but these errors were encountered: