How to get in dict format input/output scheme?

[ZeusFSX]

I faced with lack of docs, how to get scheme of input and output data.

For example, Postman has nice feature to get Example message and you can see input and output scheme
I tried to use get_method_meta, but didn't find it useful. Also, I used describe_response and describe_request, but when one of the field contain type MESSAGE, it didn't show nested structure into MESSAGE

[ViridianForge]

Are you able to include a rough example of what you were expecting to get back from an example service, just for reference / building test cases?

I think I have an idea of what you're running into, so I will give it a try when I have some free time.

[ZeusFSX]

Here the example of proto file:

service Shop {
  rpc AddItems (AddItemsRequest) returns (AddedItemsResponse);
}

message AddItemsRequest {
  repeated Item items = 1;
}

message AddedItemsResponse {
  repeated string success = 1;
  repeated string errors = 2;
}

message Item {
  string product_id = 1;
  string title = 2;
  int32 sku = 3;
  repeated Category categories = 4;
  Decimal price = 5;
}

message Category {
  int32 id = 1;
  string name = 2;
}

message Decimal {
  string value = 1;
}

When I try to invoke method:

client.describe_request("Shop", "AddItems")

I want to get something like this:

{
  "items": [
    {
      "product_id": "string",
      "title": "string",
      "sku": 0,
      "categories": [
        { "id": 0, "name": "string" },
        { "id": 1, "name": "string" }
      ],
      "price": { "value": "string" }
    }
  ]
}

When I try to invoke method:

client.describe_response("Shop", "AddItems")

I want to get something like this:

{
  "success": [
    "string"
  ],
  "errors": [
    "string"
  ]
}

[ViridianForge]

Hey @ZeusFSX - many apologies for the long delay. Took this ticket as a chance to also clean up some dependency and tech debt work.

If you're willing, take a look at this example to see if the new feature is in line with what you had in mind.

I have some documentation and naming clean up to do, but this should be up in version 0.1.22 in the near future.