You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
protoc-gen-openapi does not map path parameters that refer to request message subfields (as in "/categories/{book_key.category}/books/{book_key.name}") as expected.
Note that book_key.category and book_key.name have not been mapped to their corresponding request message subfields, which therefore also show up as query parameters (bookKey.category and bookKey.name).
As far as I know, having path parameters refer to subfields is valid. It's mentioned in http.proto and is supported by the Envoy gRPC-JSON transcoder.
The text was updated successfully, but these errors were encountered:
protoc-gen-openapi does not map path parameters that refer to request message subfields (as in
"/categories/{book_key.category}/books/{book_key.name}"
) as expected.As an example, running protoc like this:
with this proto:
produces this output:
Note that
book_key.category
andbook_key.name
have not been mapped to their corresponding request message subfields, which therefore also show up as query parameters (bookKey.category
andbookKey.name
).As far as I know, having path parameters refer to subfields is valid. It's mentioned in http.proto and is supported by the Envoy gRPC-JSON transcoder.
The text was updated successfully, but these errors were encountered: