Tags: tomarrell/wrapcheck
Tags
feat: suppress reports from unexported interface methods (#52) When an interface method is not exported, its only implementations will be local to the module under analysis. Thus, the implementations can be checked, and the caller can assume the error was wrapped. This reasoning does not apply to exported interface methods, even if the interface happens to also have an unexported method. (An implementation can override just the public methods by embedding the interface or a struct that implements it.)
deps: bump golang.org/x/text from 0.3.7 to 0.3.8 (#38) Bumps [golang.org/x/text](https://github.com/golang/text) from 0.3.7 to 0.3.8. - [Release notes](https://github.com/golang/text/releases) - [Commits](golang/text@v0.3.7...v0.3.8) --- updated-dependencies: - dependency-name: golang.org/x/text dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
feat: ignore Go 1.20 errors.Join() sig by default (#37) After upgrading to Go 1.20 and using the new `errors.Join()` from the standard library, there is a false positive from `wrapcheck` saying that error returned from external package is unwrapped, when `errors.Join()` is now supposed to be an idiomatic way to wrap multiple errors from external packages. More info in the Go 1.20 release notes: https://tip.golang.org/doc/go1.20#errors
PreviousNext