errors

ARCHIVED

This repository is now archived. If you are interested in a solution to work with rich errors, please look to https://github.com/go-extras/errx instead.

---

Package errors provides simple error handling primitives.

go get github.com/go-extras/errors

The traditional error handling idiom in Go is roughly akin to

iferr!=nil {
returnerr
}

which applied recursively up the call stack results in error reports without context or debugging information. The errors package allows programmers to add context to the failure path in their code in a way that does not destroy the original value of the error.

Adding context to an error

The errors.Wrap function returns a new error that adds context to the original error. For example

_, err:=ioutil.ReadAll(r)
iferr!=nil {
returnerrors.Wrap(err, "read failed")
}

Retrieving the cause of an error

Using errors.Wrap constructs a stack of errors, adding context to the preceding error. Depending on the nature of the error it may be necessary to reverse the operation of errors.Wrap to retrieve the original error for inspection. Any error value which implements this interface can be inspected by errors.Cause.

typecauserinterface {
Cause() error
}

errors.Cause will recursively retrieve the topmost error which does not implement causer, which is assumed to be the original cause. For example:

switcherr:=errors.Cause(err).(type) {
case*MyError:
// handle specificallydefault:
// unknown error
}

Read the package documentation for more information.

Contributing

Before sending a PR, please discuss your change by raising an issue.

License

BSD-2-Clause