Log information about the event when sending invoking a Lambda via "sls invoke"

This is a Feature Proposal

Description

Over the last couple months a sometimes ran into the issue of sending a string to instead of a JSON object when running sls invoke. I believe we can improve DX by informing people what actually gets sent.

Current Issue

sls invoke --log -s dev -f updateDesc --data '{ "id": "abc", "description": "test" }' -> Data is a JSON

In the case above the a JSON ist dedected and converted by sls invoke.

sls invoke --log -s dev -f updateDesc --data '{ "id": "abc", description: "test" }' -> Data is a String

In the case above it’s not valid JSON, because the description key doesn’t have quotes. In this case the whole thing is sent as string.

Suggestion we improve the CLI experience by doing the following:

sls invoke --log -s dev -f updateDesc --data '{ "id": "abc", "description": "test" }'

Serverless Request:
{ "id": "abc", "description": "test" } 
Serverless Response:
{
    "id": "abc",
    "name": "test-name"
    "description": "test"
}

sls invoke --log -s dev -f updateDesc --data '{ "id": "abc", description: "test" }'

Serverless Request:
'{ "id": "abc", "description": "test" }'
Hint: The data you sent is a String. If you want to send an object all keys must have quotes.
Serverless Response:
{
    "id": "abc",
    "name": "test-name"
    "description": "test"
}

[brianneisler]

Hmm, something seems off about all of this. JSON is a string… so it seems like there is either a bug somewhere or our treatment of the data parameter is a little off… will have to investigate it a bit further to understand what’s going on in that command.

That being said, I like the output with headers. The hints are kind of nice but I think type information should just be part of the output

Object {
  a: 123
}

String '{ "a": 123 }'

[pmuens]

Closing since this issue is quite old and there are no plans to support this in the foreseeable future.