Consider Rename

[sudorandom]

As the features of this project have evolved, it's now possible and reasonable to generate OpenAPI spec for both Connect and google.api.http endpoints. I can also imagine adding support for twirp in the future. The project name is a bit confusing to some since it does imply that this ONLY supports the ConnectRPC specification.

Therefore, I'm considering a rename for this project.

• sudorandom/protoc-gen-openapi
• sudorandom/protoc-gen-oapi
• sudorandom/protoc-gen-oapi3 - I'm leaning against this as oapi4 now exists and support will likely be added for it in this same repo

This list is sorted by my current preference, but I'm going to let this issue set for a bit for other suggestions and to give myself time to think about it.

[george-oakling]

sudorandom/protoc-gen-openapi

[ryanriccio1]

There's already a few protoc-gen-openapi repos that exist, including one from google under the gnostic repo. Also protoc-gen-openapiv2 is already a part of grpc-gateway, which, to the uninitiated, would make this repo sound "outdated".

[Anthony-Bible]

I agree with ryan. There are several repos already named protoc-gen-openapi so it may increase confusion on what one to use. I'm not sure I can offer an alternative.

[cyberxnomad]

Alternative suggestions:

• protoc-gen-oas
• protoc-gen-unified-openapi

However, if you don't mind the name conflict with the well-known gnostic project, I believe protoc-gen-openapi is the optimal choice. That being said, the gnostic project is barely maintained nowadays.