Øyvind Matheson Wergeland

I see the problem - we got the same problem in one of our own methods. It is also confusing because the parameter documentation is shared. Merging the paths and...

@yinzara Btw, we use readme.com for API browsing, which does show `pattern` (if set) when you enter the input field. However, as pointed out here https://github.com/grpc-ecosystem/grpc-gateway/issues/720#issuecomment-1123584733 `/` isn't allowed in...

> there is a configuration for grpc-gateway that allows you to accept escaped path parameters, That’s interesting. We use ESP, which doesn’t provide that: https://cloud.google.com/endpoints/docs/grpc/specify-esp-v2-startup-options#transcoding

Is this issue related to the gateway itself or the OpenAPI v2 generator? I've only worked on the latter, so if this is in the gateway I fear it's not...

@catundercar Can you please provide a repro with a proto file and the command to generate the OpenAPI file?

Thanks for the link. The `Makefile` only calls `protoc` with `--grpc-gateway…`, not `--openapiv2…`, this is not related to the changes done to the OpenAPI generator. Note that `**` matches _zero...

I would think so as well, but I find the specification in general a bit loose, so I would test the behaviour with e.g. ESPv1 or ESPv2 (which are implemented...

I've read this and related issues with great interest, as we also have gRPC APIs that follows the Google gRPC API guidelines with the resource name syntax (e.g. (`"/v1/{name=foos/*}"`) in...

Thanks for the feedback! My idea is not in ideal, it's merely a workaround the lack of support for this in the standards (OpenAPI and gRPC HTTP mapping). I get...

I have implemented a simpler suggestion in PR #2562