| Age | Commit message (Collapse) | Author |
|
- All wrapped errors have to be created with types.NewWrappedError to
inherit the error level from the parent
- Or types.NewWrappedErrorLevel can be used which means a custom error
level is given. For example this is done with cancelling OAuth
- Client public errors are forwarded with handleError that also logs
it with the error's level
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- We should never panic now because there is no way to set an extra
key for testing
- This was not used anyways in the Go code, and we should never expose
an insecure function to wrappers
|
|
- For this an `internal/types` package is created with a custom error type
- This custom error type can give back the cause and traceback of an error
|
|
|