oapi-codegen VS pushup

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.

We're using https://github.com/deepmap/oapi-codegen at work while having an OpenAPI spec. When the spec changes, backend/frontend/mobile regenerate their server/client

I think this is adding unnecessary complexity. One of the reasons developers gravitate towards a framework like Alpine or HTMX is to write less JS and go back to enjoying HTML. Of course there are a lot of use cases that require custom JS scripting. But bootstrapping a project with another Go web framework and adding Alpine is also trivial. But keep going and follow your vision. I love these types of projects. Check this one out:

https://pushup.adhoc.dev

It's got some unique ideas.

This strikes me as incredibly clever.

The compiler and code-generation implementation seems equally straightforward and complex, my mind is racing trying to build a mental model of the whole thing.

The code generation comes after a feature-packed parser and "compilation" step. Emitting go source code is nice because subsequent compilation tells you if its valid or not. I'm wondering if there is a specific reason the "framework" source code is emitted via a series of printf calls[0]. A library of go template "fragments" might be easier to manage (and debug).

[0] https://github.com/adhocteam/pushup/blob/0519a782c1c9fc79877...