Question 1

How to ignore test files in errcheck?

Accepted Answer

Use the -ignoretests flag to disable checking of _test.go files. This helps focus on production code errors without noise from test files, as documented in the command-line options.

Question 2

errcheck vs staticcheck for error handling?

Accepted Answer

errcheck focuses solely on unassigned errors, while staticcheck offers broader static analysis including error usage and more. Use errcheck for strict assignment checks, but staticcheck for comprehensive linting beyond errors.

Question 3

How to exclude vendor dependencies in errcheck?

Accepted Answer

Specify the full import path in the exclude file, including the vendor directory. For example, add 'example.com/yourpkg/vendor/example.net/fmt2.Println' to ignore functions from vendored packages, as explained in the README.

Question 4

Does errcheck work with Go modules?

Accepted Answer

Yes, errcheck supports Go modules and can be installed via go install. Use the -mod flag to set the module download mode if needed, ensuring compatibility with modern Go workflows.

Question 5

Best practices for errcheck exclude lists?

Accepted Answer

Start with the built-in exclusions for standard library functions, then add project-specific ignores in a separate file. Use the -verbose flag to review what's being excluded and avoid missing critical errors.

Question 6

How to integrate errcheck into a CI pipeline?

Accepted Answer

Run errcheck with appropriate flags like -exclude and -tags in your build script, and check the exit code (1 for errors found) to fail the build on unchecked errors, ensuring consistent error handling enforcement.

errcheck

What is errcheck?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions