DocService Add collapsible grpc request / response types

[Dogacel]

Proto response/request types are not collapsible. I think they should automatically become collapsible because those types do not contain any valuable information and most of the time they are just {METHOD_NAME}Request and {METHOD_NAME}Response.

Example:

[minwoox]

So do you mean we need to make the Parameters and Return Type sections collapsible?

[Dogacel]

I mean, we should be able to see the fields inside AddDishRequest and AddDishResponse in that single page as we do for Dish type. Because each RPC method has one request and one response type, it would save everyone a click.

Also the convention is not using primitives for requests/response types. For each rpc method XXX, the return type would be XXXResponse and request type would be XXXRequest. Google API Guide Buf Style Guide

[minwoox]

Now I get what you meant. 😄
Thanks for the nice suggestion.
It perfectly makes sense if we use this DocService for a gRPC service only.
However, we also use this for an annotated service or a Thrift service which might have a bunch of parameters.
In that case, the unfolded structs would make the page cumbersome.

[Dogacel]

@minwoox makes sense, can we make this appear conditionally (e.g. show it only in grpc methods) by using some sort of boolean flag?

I also realized the section Exceptions is always empty (maybe I have missed something) for grpc methods, we can also hide that.