How to customize operationId for a PUT and a PATCH rpc

[saltbo]

📚 Documentation

(A clear and concise description of what the issue is.)

I have a rpc method like below, it supports both PUT and PATCH calls. I want to customize the operationId, like below. but the result is there is a repeated operateId in the generated apidocs.swagger.json.

How do I define these two operateIds separately?

  // Update updates a function.
  rpc Update(UpdateFunctionRequest) returns (Function) {
    option (google.api.http) = {
      put: "/api/v1/functions/{id}"
      body: "function"
      additional_bindings: {
        patch: "/api/v1/functions/{id}"
        body: "*"
      }
    };
    option (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_operation) = {operation_id: "updateFunction"};
  }

PS: Duplicate ids will cause failure in client generation

Errors: 
	-attribute paths.'/api/v1/functions/{id}'(patch).operationId is repeated
	at org.openapitools.codegen.config.CodegenConfigurator.toContext(CodegenConfigurator.java:620)
	at org.openapitools.codegen.config.CodegenConfigurator.toClientOptInput(CodegenConfigurator.java:647)
	at org.openapitools.codegen.cmd.Generate.execute(Generate.java:479)
	at org.openapitools.codegen.cmd.OpenApiGeneratorCommand.run(OpenApiGeneratorCommand.java:32)
	at org.openapitools.codegen.OpenAPIGenerator.main(OpenAPIGenerator.java:66)

[johanbrandhorst]

There's no way to do this with our current schema. Can you create to separate RPCs? I don't think we can support this.

[saltbo]

We don't want to recreate a duplicate RPC, it's same method!

I found that when we do not manually set the operationId, the generated swagger document will have operationIds as update1 and update2. When we define them manually, they are both updateFunction, not updateFunction1 and updateFunction2.

I think this behavior should be fixed.

[johanbrandhorst]

I'm sympathetic, but I don't know that there's any way that we can support it. Can I suggest you post-process the generated file?