Explore >> Select a destination
|
You are here 
|
dmitryfrank.com | ||
| | | | |
alexrichey.com
|
|
| | | | | A pattern for distinguishing and handling client and internal errors in Go that leverages the power of Go's interfaces. | |
| | | | |
linksort.com
|
|
| | | | | In writing a REST API, we have to deal with at least two types of errors. Client errors: These errors are the fault of the user, e.g., providing an invalid... | |
| | | | |
www.morling.dev
|
|
| | | | | Update Jan 13: This post is discussed on Reddit Update Feb 7: This post is discussed on Hacker News As software developers, we've all come across those annoying, not-so-useful error messages when using some library or framework: "Couldn't parse config file", "Lacking permission for this operation", etc. Ok, ok, so something went wrong apparently; but what exactly? What config file? Which permissions? And what should you do about it? Error messages lacking this kind of information quickly create a feeling... | |
| | | | |
syntackle.com
|
|
| | | You might be familiar with functions in JavaScript. An IIFE is a special type of function which is invoked implicitly. | ||
