typescriptify-golang-structs VS oapi-codegen

I've used https://github.com/tkrajina/typescriptify-golang-structs and it's worked for me so far, relatively simple so you can be up in minutes.

I have been looking into various ways of doing this properly, including openapi, swagger and grpc, connect-go etc. My conclusion is that these are overkill for this project and that something like https://github.com/tkrajina/typescriptify-golang-structs which generates typescript definitions from go structs, are probably more than enough.

I use this tool to compile go structs to typescript types for integration w frontend

I'm curious if you looked at https://github.com/tkrajina/typescriptify-golang-structs, and if so, what it does that you didn't want.

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.