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

After expanding the set of tags (`-include-tags`) that we generate code for, the type prefix that used to appear on enum constants vanishes, breaking existing code. The unexpected changes are...

Hello Thank you for your work, I created a repository that reproduces my issue, you can find it in here: https://github.com/gianarb/repro-oapi In practice if you check the openapi.yaml spec you...

Hello, I have an OpenAPI spec that has a bunch of endpoints like this: ```json "paths": { "/api/v1.0/Application/{id}": { "post": { ... } "get": { ... } "/api/v1.0/Application/{id}/providers": { "get":...

When using referencing, e.g.: ``` "properties": { "$ref": "#/components/schemas/Properties", "x-order": 2 }, ``` Then the x-order is not respected. Only if it is put on the actual referenced feature `Properties`....

https://github.com/deepmap/oapi-codegen/issues/1607 x-order is given as a solution for the above issue. But even after giving x-order still the order of the props coming in alphabetic order instead of what mentioned...

Right now if a schema contains `x-go-type`, for example: ``` components: schemas: Pet: x-go-type: pet.Pet x-go-type-import: path: github.com/somepetproject/pkg/pet type: object required: - pet_type properties: pet_type: type: string discriminator: propertyName: pet_type...

when security is defined in the openapi yaml like the following ```yml paths: /foo: get: # ... security: - key: [] secret: [] components: securitySchemes: key: type: apiKey in: header...

As briefly discussed [there](https://github.com/deepmap/oapi-codegen/issues/1584) The current behavior of the code generation is a mix between always required and always optional bodies. However the open api specification is pretty clear about...

request bodies should be optional by default see https://spec.openapis.org/oas/v3.1.0#fixed-fields-10 or https://swagger.io/docs/specification/describing-request-body/ but as we can see here https://github.com/deepmap/oapi-codegen/blob/621b44626ac9a1aa6c9fdda97324a58569227281/pkg/codegen/templates/strict/strict-http.tmpl#L50, we check that a content type is set only when multiple request...

server:strict

I.e. We'll try and release monthly? Whenever we feel like it? Whenever there are more than 10 changes?

documentation
internal