For example an RPC like this
service MapService {
rpc Search(SearchRequest) returns (SearchResponse) {
option (google.api.http) = {
get: "/v1/search"
};
}
}
message SearchRequest{
repeated Coordinate polygon = 1;
}
message Coordinate {
float lat = 1;
float lon = 2;
}
is expected to be callable using http protocol in the following manner: https://example.com/v1/search?polygon[0][lat]=55.11&polygon[0][lon]=55.22 but at the moment fields with repeated custom messages are just ignored from generated http server and swagger spec.
For example an RPC like this
is expected to be callable using http protocol in the following manner:
https://example.com/v1/search?polygon[0][lat]=55.11&polygon[0][lon]=55.22but at the moment fields with repeated custom messages are just ignored from generated http server and swagger spec.