oapi-codegen
GoSwagger
Our great sponsors
oapi-codegen | GoSwagger | |
---|---|---|
63 | 25 | |
5,068 | 9,225 | |
5.3% | 1.2% | |
9.0 | 8.8 | |
4 days ago | 9 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oapi-codegen
-
AsyncAPI Codegen, a code generator from AsyncAPI spec v2 and v3.
During daytime, and especially work time, I used a great tool to generate code from OpenAPI specification: deepmap/oapi-codegen.
-
Created an API using Gin, want to create sdk for him
Then you can use oapi-codegen or openapi-generator to generate the Go (or other language) SDK for it.
-
Create Production-Ready SDKs with Goa
Deepmap OpenAPI code generator
-
Manage DEV Articles with Git and GitHub Actions
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:
-
Openapi server generation
For Go, I've found https://github.com/deepmap/oapi-codegen/, and it works well.
-
Combining oapi-codegen, echo and validator frameworks to build robust APIs
Iβm using oapi-codegen in my project and I donβt think it ships with a validator.
-
Sharing types between Go backend and TypeScript frontend: best practices and tools?
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
- Why is gin so popular?
-
what's your recommended router? chi, mux, something else?
I use oapi-codegen with Echo
-
Golang tech stack
Deepmap oapi-codegen if I'm using OpenAPI
GoSwagger
-
OpenAPI v4 Proposal
Much or some OpenAPI tooling has not even moved past OpenAPI 2.0 some even refusing and saying that they will not update to Swagger 3.0 [0] and others have issues open since some 2019 and still open with no resolution in sight (because these are individuals doing out of passion and the spec is complex to implement) and yet we have Open API spec 4.0
All this is - trying to do RPC over HTTP in a fashion that was deemed virtuous in some doctoral thesis.
I wish there were better alternatives for RPC that work everywhere including browsers.
[0]https://github.com/go-swagger/go-swagger/issues/1122#issueco...
-
[Request] Library Recommendation for Auto Swagger/OpenAPIv3 Documentation
I recommend this: https://github.com/go-swagger/go-swagger
-
A there any production-ready code generators?
Hi there. I am seeking any open source Schema Driven Development tool like go-swagger, but i really need to use there:
- Is there a way to generate controller from swagger through build tools?
-
FastAPI Replacement - especially with openapi
Try this https://github.com/go-swagger/go-swagger. It generates code for you. It is useful if only for you to generate the models/structs you could use.
-
OpenAPI Specification: The Complete Guide
go-swagger brings to the go community a complete suite of fully-featured, high-performance, API components to work with a Swagger API: - Github - Swagger 2.0 implementation for go
-
Easiest way to make a documentation?
There is also a Code Generator that reads in a swagger file (2.0 only) and generates code for you, so all you have to do is create functions.
This is the fastest way; it isn't necessarily the best for an API, because godoc is designed to document Go code, not HTTP APIs. You can use something like go-swagger to try to generate swagger/OpenAPI documentation. However, I find it a useful package, but a frustrating one to use. It likes to silently fail and just stop generating documentation and imposes a couple of restrictions the underlying spec doesn't. I find I have to make one change at a time and run their generator after each one, because at any moment, I may make a small typo, or confuse it some other way, and lose entire chunks of my documentation silently. But when it is working, it is an option for documenting APIs.
-
Show me your REST APIs π
You have things like https://github.com/go-swagger/go-swagger. Where the generated code is not 100% vanilla, not ideal.
-
Looking for help with Azure Autorest
You may have better luck with go-swagger or OpenAPI Generator to generate Go code.
What are some alternatives?
swag - Automatically generate RESTful API documentation with Swagger 2.0 for Go.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
go-kit - A standard library for microservices.
kin-openapi - OpenAPI 3.0 (and Swagger v2) implementation for Go (parsing, converting, validation, and more)
goa - π Goa: Elevate Go API development! π Streamlined design, automatic code generation, and seamless HTTP/gRPC support. β¨
ogen - OpenAPI v3 code generator for go
go-oas3 - Open API v3 server code generator
autorest - OpenAPI (f.k.a Swagger) Specification code generator. Supports C#, PowerShell, Go, Java, Node.js, TypeScript, Python