Explore >> Select a destination
|
You are here 
|
lewisdale.dev | ||
| | | | |
mfbmina.dev
|
|
| | | | | Nowadays, a huge part of a developer's work consists in calling APIs, sometimes to integrate with a team within the company, sometimes to build an integration with a supplier. The other big role in daily work is to write tests. Tests ensure (or should guarantee :D) that all the code written by us works on how it is expected and, therefore, it will not happen any surprises when the feature is running at production environment. | |
| | | | |
hjr265.me
|
|
| | | | | I know many will start with something like Gin whenever they are working on a JSON/HTTP-based backend in Go. I, not entirely sure if the minority, try to stick to Go's built-in net/http package and, at most, use Gorilla Mux in most of my Go projects. And so serving something simple like JSON is no different from the package's point of view as any other content type: whatever it is, write it out to the w, the http. | |
| | | | |
www.alexedwards.net
|
|
| | | | | [AI summary] The article demonstrates various Go web application techniques including HTTP response handling, templating, and file serving with examples and code snippets. | |
| | | | |
www.ardanlabs.com
|
|
| | | I wanted to send an email from my TraceLog package when a critical exception occurred. Fortunately Go's standard library has a package called smpt which can be found inside the net package. When you look at the documentation you are left wanting. I spent 20 minutes researching how to use this package. After fighting through the parameters and bugs, I came up with this sample code: package main import ( | ||
