We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's common to call context.succeed context.error and context.done with an object instead of a string.
context.succeed
context.error
context.done
The lambda invoke task fails to output them, instead just printing the following
Success! Message: ------------------ [object Object]
I think the output objects should be serialized so you get some sane output.
The text was updated successfully, but these errors were encountered:
According to the AWS Lambda documentation the result provided must be JSON.stringify compatible so 👍 for #55
JSON.stringify
Sorry, something went wrong.
Thanks for reporting this issue.
It should be resolved by this pull request in the next release: f544e42
No branches or pull requests
It's common to call
context.succeed
context.error
andcontext.done
with an object instead of a string.The lambda invoke task fails to output them, instead just printing the following
I think the output objects should be serialized so you get some sane output.
The text was updated successfully, but these errors were encountered: