`-d nested-json-string` error getting request data about grpcurl HOT 4 CLOSED

@Harold2017, looks to me like you are using the tool correctly.

That error message means that, while trying to unmarshal the JSON data into a request, it encountered the start of an object -- the curly brance { -- where it was expecting a string value. It expects string values as keys in an object (i.e. field names) and also for fields whose type in the protobuf source is string or bytes.

I can't help you troubleshoot further without a small repro case that includes the protobuf source for the service and message and a JSON payload that triggers the error.

from grpcurl.

@jhump , many thanks!
If i want to accept this request json as string on server side like the following .proto presents:

// reception
message Command {
    string appid = 1;  // sender tag
    string jsonData = 2;  // json string
    string others = 3;
}

do i need to change the reception type to struct jsonData = 2 ?

I will try it later and update to you, thanks!

from grpcurl.

@Harold2017, yes, you'd need to import "google/protobuf/struct.proto" and then define the field's type as google.protobuf.Struct. That allows it to represent any JSON object.

As is, defined as a string, you'd need to nest that field's JSON payload into a string. Like so:

{
  "appid": "foo",
  "jsonData": "{ \"nested\": \"json\" }",
  "others": "bar"
}

from grpcurl.

@jhump You're right! Many thanks!

from grpcurl.