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.22
but at the moment fields with repeated custom messages are just ignored from generated http server and swagger spec.