Repository navigation
Http Rule: map in URL parameter #1187
git-torrent
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
documentation of http GET mapping at https://github.com/googleapis/googleapis/blob/master/google/api/http.proto#L113 says
// Note that fields which are mapped to URL query parameters must have a
// primitive type or a repeated primitive type or a non-repeated message type.
// In the case of a repeated type, the parameter can be repeated in the URL
// as
...?param=A¶m=B. In the case of a message type, each field of the// message is mapped to a separate parameter, such as
//
...?foo.a=A&foo.b=B&foo.c=C.Map is technically a non-schematic message falling into non-repeated message type. This is, however, not explicit and some transcoders (e.g. in Envoy) behave as if it were repeated message type, what is disallowed by this spec. Can the documentation be updated to explicitly specify this?
All reactions