chi VS kin-openapi

I use go-chi for handling routes and to server static file(stylesheet).

This will be the structure of our project, we will use PostgreSQL as the database, go chi to create our endpoints, go dot env to import our environment variables.

go-chi: is a lightweight, idiomatic and composable router for building Go HTTP services.

Go Chi para criar nossas rotas

For HTTP I'd look at Chi https://github.com/go-chi/chi

In fact, it has zero dependencies outside of std lib in it's core: https://github.com/go-chi/chi/blob/master/go.mod

Interesting. go-chi added it as a middleware 4 months ago, but its not in the module docs since they haven't tagged a version since Dec 2022: https://github.com/go-chi/chi/blob/master/middleware/request_size.go

We'll use the excellent kin-openapi Go library to convert the OpenAPI 2.0 schema to OpenAPI 3.0.

What is your language?

I've found kin-openapi to be good for Go:

https://github.com/getkin/kin-openapi

I recently used https://github.com/getkin/kin-openapi openapi2 and openapi2conv to convert the v2 yaml to v3 yaml.

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.

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).

Then define the corresponding YAML/JSON specification (again manually) either using Swagger 2.0 (with go-swagger) or OpenAPI 3 (with kin-openapi), and