errors VS problem

I have errors too ) https://github.com/nikandfor/errors

Full code with few tests is here

I did the same :)

I have errors package too.

I want to add that when wrapping error you should add function name you've called not function name you are in. Caller of your function already knows what he is called and he'll wrap it if he needs to. Or even better use human message and function name you can get out of Program Counter attached to the error. Non-stdlib errors package can do that (I use my own).

By the way I've experimented with errors either.

The approach I tried for APIs was to do the opposite, and have the DB layer use an error type which includes an appropriate HTTP status code and details of exactly what's wrong as well as the regular error value.

If your goal is to report more meaningful structured errors to a REST API caller, you might find this helpful.

Check out https://github.com/lpar/problem

You might find this helpful.

Alternative which implements RFC 7807

For a web service, try RFC 7807. I've got a library to help implement it. A similar approach could help with regular application errors too.

The best thing is to make your REST API respond as per RFC 7807 (helper Go library here), which gives you a standard way to add human-readable error messages. If the error should be displayed on a web page, handle that client-side using JavaScript DOM manipulation.