Definitions containing URLs with trailing slashes won't compile

[zweizeichen]

Hi,
Thank you for maintaining this project! Just a quick question. I just tried compiling my definition containing a URL containing a trailing slash:

get: "/v1/my/endpoint/param/{param_value}/"

When I try to compile that definition, I get this error:

--grpc-gateway_out: segment neither wildcards, literal or variable: expected "{" but got "\x00": /v1/my/endpoint/param/{param_value}/

See: parse.go:150
Seems like it does not expect the segment started by the trailing slash to end instantly. Without the trailing slash everything just works. Is this a deliberate design choice or simply a bug? If it is a design choice, providing a more helpful error message might be a good idea. If it's a bug, it should be fairly easy to fix.

[tamalsaha]

@zweizeichen , gateway follows Google's http.proto spec https://github.com/googleapis/googleapis/blob/master/google/api/http.proto#L214

This spec does not allow trailing slash.

[zweizeichen]

Thanks! That answers my question.