Describe the bug
There will be many operations in an openapi spec that will have multiple responses without any body. Think about any delete operation. Normally it won't have any response with a content.
While generating go code from such an openapi spec, openapiart throws errors.
The error comes from a malformed protobuf file which is generated in the process.
It generates message definitions with multiple string fields with the same name viz., string.
To Reproduce
Just add a delete operation with an openapi spec with multiple empty responses and see the issue to happen..
Expected behavior
A valid protobuf file should be generated and entire go code generation process should go through.
Version information v0.2.24
Describe the bug There will be many operations in an openapi spec that will have multiple responses without any body. Think about any delete operation. Normally it won't have any response with a content.
While generating go code from such an openapi spec, openapiart throws errors.
The error comes from a malformed protobuf file which is generated in the process.
It generates message definitions with multiple
stringfields with the same name viz.,string.To Reproduce Just add a delete operation with an openapi spec with multiple empty responses and see the issue to happen..
Expected behavior A valid protobuf file should be generated and entire go code generation process should go through.
Additional context None