[Bug]: OpenAPI spec does not follow proper OpenAPI specifications

[Olshansk]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

tl;dr We tried and gave up on using an auto SDK generator that uses the OpenAPI spec as a basis.

---

This is a request to revisit if the OpenAPI spec autogenerated follows proper specifications.

Related links:

• Is swagger.yml really correct? #6131
• REST API endpoint swagger does not respond #17611
• Related documentation

  If, for various reasons, you cannot use gRPC (for example, you are building a web application, and browsers don't support
  HTTP2 on which gRPC is built), then the Cosmos SDK offers REST routes via gRPC-gateway.

• Exploration
• Feedback from team at https://buildwithfern.com/:
  

Cosmos SDK Version

0.47

How to reproduce?

Non-trivial amount of effort.

1. Use the auto-generated OpenAPI spec at ./docs/static/openapi.yml
2. Follow the instructions at https://buildwithfern.com/ to auto-generate a golang and typescript SDK
3. An example can be found at pokt-network/poktroll/pull/344

[tac0turtle]

Hey we are using a generator for this: https://github.com/grpc-ecosystem/grpc-gateway/tree/main/protoc-gen-openapiv2. We dont write it manually so i can see there may be bugs, but since we try to avoid touching generated code there may not be anything we can do unless the dependency updates

[Olshansk]

@tac0turtle Noted.

I opened this this issue in Fern.

If time ever permits me to do it myself, I'll look into it, but it would be closer to the end of the year unless someone in their ecosystem looks into it.