When using the latest version of protoc-doc-gen to generate markdown for a .proto file, the links for the response and request messages are both the same: they are both a link to the request message.
The following snippet is part of a markdown file generated by the proto file shown further below:
syntax = "proto3";
package example;
import "google/api/annotations.proto";
service ExampleService {
// Deletes a book.
rpc DeleteBook(DeleteBookRequest) returns (DeleteBookResponse) {
// Delete maps to HTTP DELETE. Resource name maps to the URL path.
// There is no request body.
option (google.api.http) = {
// Note the URL template variable capturing the multi-segment name of the
// book resource to be deleted, such as "shelves/shelf1/books/book2"
delete: "/v1/{name=shelves/*/books/*}"
};
}
}
message DeleteBookRequest {
// The resource name of the book to be deleted, for example:
// "shelves/shelf1/books/book2"
string name = 1;
}
message DeleteBookResponse {
// The resource name of the book deleted, for example:
// "shelves/shelf1/books/book2"
string name = 1;
}
When using the latest version of protoc-doc-gen to generate markdown for a
.proto
file, the links for the response and request messages are both the same: they are both a link to the request message.The following snippet is part of a markdown file generated by the proto file shown further below:
DeleteBookRequest
DeleteBookResponse
ExampleService
Notice the links in the RPC? Look at the source:
DeleteBookResponse links to DeleteBookRequest.
example.proto: