oapi-codegen
oapi-codegen copied to clipboard
deepmap
Generate Go client and server boilerplate from OpenAPI 3 specifications
When generating client code defined through swagger 3.0, the **runtime.MarshalForm** method will marshal the values of type slice in the form structure into **field_name[index]**, but the server cannot handle such...
Currently, the oapi-codegen tool will generate a pointer to a slice of types. This is unnecessary, as slices are already reference values, [per the language spec](https://go.dev/doc/effective_go#slices) This gives the ability...
Hi, I have been wanting to test to generate a client for this specification, sadly it failed. I think compared to the https://github.com/OpenAPITools/openapi-generator generator this one is way better as...
For https://github.com/deepmap/oapi-codegen/issues/1362 OpenAPI specifications can be spread across different files for maintainability. However this is not great for code-gen which can't recognise when two schema refs refer to the same...
As it ends up generating code that can't compile. Alternatively, make it _implied_?
``` - exploded, form style query arguments, which are the default argument format in OpenAPI 3.0 are undecidable. Say that I have two objects, one composed of the fields `(name=bob,...
As part of the v3.0.0 release, we should default to a stdlib-only generation, rather than Echo (as per https://pkg.go.dev/github.com/deepmap/oapi-codegen/v2/pkg/codegen#Configuration.UpdateDefaults)
To make builds reproducible, and to make it so folks have to opt-in
Via / until #1521 it'd be useful to report which templates are being used, and what's being ignored / isn't default locations