How I Learned Generics in Go

• automated-garden

  1 19 9.2 Go

  weather-based smart irrigation controller and backend

When thinking about duplicated code in my automated-garden project, the first thing that comes to mind is all of my API handlers. The server side of this application implements a few straightforward CRUD APIs following RESTful principles. Each resource type implements handlers for the different HTTP verbs and mostly interacts with the storage layer. I created a very simple setup for the API handlers following this formula:

• render

  3 273 2.0 Go

  easily manage HTTP request / response payloads of Go HTTP services (by go-chi)

  

GET endpoints just use go-chi/render to create the HTTP response

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• hord

  2 15 8.1 Go

  Manage data in Go with a simple key-value interface supporting various databases.

Determined to implement generics and delete some lines of code, I turned my sights to the storage layer of my application. I designed my storage around key-value pairs since I started by storing resources in YAML files. This eventually evolved to use madflojo/hord to interact with key-value data stores like Redis. The function to read a *pkg.Garden from storage looks like this:

Suggest a related project