be VS oapi-codegen

For testing, use be

I made a package like that: https://github.com/carlmjohnson/be. It’s probably my most frequent use of generics.

I spent the last week working on one of these: https://github.com/carlmjohnson/be. Some initial thoughts I have are that the error messages basically don’t matter because if the test fails you’re going to dig into the line where the failure happens anyway.

what’s the difference between this and https://github.com/deepmap/oapi-codegen

During daytime, and especially work time, I used a great tool to generate code from OpenAPI specification: deepmap/oapi-codegen.

Then you can use oapi-codegen or openapi-generator to generate the Go (or other language) SDK for it.

Deepmap OpenAPI code generator

Luckily, Forem/DEV is open source and provides great API documentation and specification. I used oapi-codegen to automatically generate a Go API client. Then, I simply had to walk the root articles directory and:

I'm using https://github.com/deepmap/oapi-codegen to auto gen some types for my api as I want the contract to be the source of truth. However, I'm running into an issue, the same as (https://stackoverflow.com/questions/77237210/how-to-generate-models-from-openapi-with-ref) where oapi-codegen isn't recognizing references to local files. Has anyone run into this and found a work around? or is there a better tool to use for this

For Go, I've found https://github.com/deepmap/oapi-codegen/, and it works well.

I’m using oapi-codegen in my project and I don’t think it ships with a validator.