My services usually involves fairly complex dependencies to other services so reusing oas typing from deps is often necessary for a meaningful end result w/o needless duplication.
With my annotated approach I meant that I am producing also openapi, but from the actual typing instead of matching my typing to a separate oas which would be compiled into types.
What is an oas ? So you write types in your main language, then generate openapi from them and maybe generate sdks from the generated openapi? that sounds good too
Something like this could work for golang as the annotated approach, but do note that I didnt do much research on the package otherwise and better options may exist for go
Comments
I am wondering if you do it in Go and if I can stop writing YAML instantly and generate openapi yaml from the generated openapi types 😅
Something like this could work for golang as the annotated approach, but do note that I didnt do much research on the package otherwise and better options may exist for go