swagger2markup
kin-openapi
| swagger2markup | kin-openapi | |
|---|---|---|
| 2 | 6 | |
| 2,480 | 2,383 | |
| 0.3% | 1.3% | |
| 1.8 | 8.5 | |
| about 2 years ago | 10 days ago | |
| Java | Go | |
| Apache License 2.0 | MIT License |
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.
swagger2markup
-
API documentation platforms/authoring stacks
I'm already up to my elbows in AsciiDoc/Antora building a new online help platform, and I noticed that Swagger2Markup exists. No idea if it's any good, but I might be able to integrate it into my existing workflow and spit out some usable static content at the other end...
-
They must hate the JS part in JSON
There are ways to generate a pdf from an OpenAPI-definition. You could use something like swagger2markup. But be warned that this approach has a pretty limited flexibility, the tools are often badly supported and it may involve a lot of work.
kin-openapi
-
Create Production-Ready SDKs With gRPC Gateway
We'll use the excellent kin-openapi Go library to convert the OpenAPI 2.0 schema to OpenAPI 3.0.
-
OpenAPI Generator allows generation of API client libraries from OpenAPI Specs
What is your language?
I've found kin-openapi to be good for Go:
https://github.com/getkin/kin-openapi
-
swaggo/swag alternative, but should generate OpenAPI 3.0 spec file
I recently used https://github.com/getkin/kin-openapi openapi2 and openapi2conv to convert the v2 yaml to v3 yaml.
-
Any good OpenAPI 3.x spec generator for a Go REST API?
This might not be very helpful, but I've have found every "generate spec from code" package to be limited sooner or later, and that's across languages. I finally settled on writing the spec file by hand, linting it in CI using openapi-cli, and using kin-openapi in Go tests to ensure responses match their schema.
-
What are your favorite packages to use?
oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).
-
Do you use swagger to generate backends?
Then define the corresponding YAML/JSON specification (again manually) either using Swagger 2.0 (with go-swagger) or OpenAPI 3 (with kin-openapi), and
What are some alternatives?
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
GoSwagger - Swagger 2.0 implementation for go
widdershins - OpenAPI / Swagger, AsyncAPI & Semoasa definitions to (re)Slate compatible markdown
chi - lightweight, idiomatic and composable router for building Go HTTP services
archifacts - archifacts is a library to extract your architectural concepts out of your application's code
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
grape-swagger - Add OAPI/swagger v2.0 compliant documentation to your grape API
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.
toml.io - Source Code for toml.io
schedge - API for NYU's course catalog
ginkgo - A Modern Testing Framework for Go