null VS chi

Use-case: working on PATCH requests, the body may or may not contain nullable values. I am using guregu/null and I can't use a pointer because if the json contains "null" as a value, the pointer will be set to nil in the struct, instead of a value representing the presence of null. In short I can't differentiate the absence of the field in the request from the presence of the field with a null value.

https://github.com/guregu/null is an awesome package implementing most SQL scanner Interfaces plus JSON

There’s also this: https://github.com/guregu/null

Unfortunately in Go, switching to *bool makes the api a little more awkward to use since users that need to set true or false have to define a local variable then use a pointer to that. Another option would be something like null, but that adds a dependency to your currently-dependency-free project. If anyone has a better solution to this pattern, I'd love to hear it.

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