oapi-codegen icon indicating copy to clipboard operation
oapi-codegen copied to clipboard

Generate Go client and server boilerplate from OpenAPI 3 specifications

Results 633 oapi-codegen issues
Sort by recently updated
recently updated
newest added

Resolve [issue](https://github.com/oapi-codegen/oapi-codegen/issues/1743), is translates `*` as `...` for `std/http`

Follow-up to https://github.com/oapi-codegen/oapi-codegen/pull/1957

This: ```yaml components: schemas: String: type: string Thing: type: object properties: x: $ref: "#/components/schemas/String" nullable: true required: - x ``` Produces a structure with a non-pointer field, but the nullable...

bug
upstream

This PR adds Fiber v3 support to oapi-codegen. While Fiber v3 is not yet production ready per [link](https://github.com/gofiber/fiber?tab=readme-ov-file#%EF%B8%8F-attention), any code changes concerning oapi code generation should've been easy to manage....

Is there an example or configuration showing how to use echo.Context with the StrictServerInterface generated by oapi-codegen?

help wanted
documentation
server:echo
server:strict

> For posterity, this still can occur when using the Client generation, i.e.: > > ``` > internal/endoflifedate/client/client.gen.go:976:6: ProductResponse redeclared in this block > internal/endoflifedate/client/client.gen.go:187:6: other declaration of ProductResponse >...

documentation
client

Version: 2.4.1 Issue: Status code is set to 200 before marshalling data into body inside visit functions, so when an error occurs marshalling the ResponseErrorHandlerFunc cannot set the status code....

### Current Setup 1. Our schema structure: ```txt schemas/ |- constructs/ |- v1beta1/ |- model.json # References core.json definitions |- openapi/ |- models.yml # Main OpenAPI schema file ``` 2....

When using `allOf` to embed other schemas, the description field of parent schema in the yaml file is not used as a comment for the generated struct. For example, given...

I use this library on sever side, while on client side do manually since the client is for mobile platform. This is my openapi spec : I follow [openapi documentation](https://swagger.io/docs/specification/authentication/bearer-authentication/)...

authN/authZ/securitySchemes