fuego

I have been experimenting with Open API spect -> CLI too. I have Go and specs auto-generated either with Huma or Fuego https://github.com/danielgtaylor/huma https://github.com/go-fuego/fuego The restish tool by the author of Huma is functionally correct, but I'm finding the models are not doing a great job at inferring the syntax. Admittedly I am having a hard time following the syntax too. https://github.com/rest-sh/restish I need to do proper evals, but it makes me wonder if `curl` or a CLI with more standard args / opts parsing will work better. Thanks to Cloudflare for sharing their notes, anyone else figure this out?

It depends on the framework and other stuff around it but you're right about the API documentation issue, there's godoc if you want to document functions but for something like API endpoints it's not what you'd find from openapi/swagger unless whatever you're using is adaptable to that and then whenever I was working with it an older spec of it too. Always fun to run into a client who expects this from working with most of their people and you're just drooling like a gopher at them but for now if you're writing something in go for pure performance I'm not 100 on what balances best between that and auto spec... Definitely choose an API framework in go that works out of the box for that if it's important. This may be better than when I tried it a couple years back https://github.com/swaggo/swag And this one seems to generate documentation f

https://huma.rocks/ https://github.com/go-fuego/fuego

I started this project because none of Chi, Echo or Gin were capable of generating the OpenAPI specification from source code. Relying on comments and explicit generation creates errors and noise when communicating with the frontend team. After a while, I started doing frontend directly in Go with HTMX & Templ/Gomponents, so I decided to adapt the framework for this use case too! You can find the project here: https://github.com/go-fuego/fuego Fuego's main features are: Automatic generation of OpenAPI documentation from code Fully net/http compatible Simplified serialization Validation (go-playground/validator + custom method) Centralized error handling I know most gophers are net/http purists, but I hope you'll like it! Don't hesitate to open issues, as some features may be missing.