wrapcheck

A Go linter to check that errors from external packages are wrapped (by tomarrell)

Wrapcheck Alternatives

Similar projects and alternatives to wrapcheck

  1. CodeRabbit

    CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

    CodeRabbit logo
  2. Benthos

    Discontinued Fancy stream processing made operationally mundane [Moved to: https://github.com/redpanda-data/connect]

  3. golangci-lint

    Fast linters runner for Go

  4. zap

    54 wrapcheck VS zap

    Blazing fast, structured, leveled logging in Go.

  5. websocketd

    Turn any program that uses STDIN/STDOUT into a WebSocket server. Like inetd, but for WebSockets.

  6. Bunyan

    13 wrapcheck VS Bunyan

    a simple and fast JSON logging module for node.js services

  7. chock

    Golang Result handling package

  8. SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  9. revive

    🔥 ~6x faster, stricter, configurable, extensible, and beautiful drop-in replacement for golint

  10. json-log-explorer

    UI for exploring JSON logs

  11. errcheck

    errcheck checks that you checked errors.

  12. emperror

    The Emperor takes care of all errors personally

  13. dockle

    Container Image Linter for Security, Helping build the Best-Practice Docker Image, Easy to start

  14. go-critic

    The most opinionated Go source code linter for code audit.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better wrapcheck alternative or higher similarity.

wrapcheck discussion

Log in or Post with

wrapcheck reviews and mentions

Posts with mentions or reviews of wrapcheck. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-22.
  • Structured Logging with Slog
    11 projects | news.ycombinator.com | 22 Aug 2023
    This is such an infuriating problem. I'm convinced I'm using Go wrong, because I simply can't understand how this doesn't make it a toy language. Why the $expletive am I wasting 20-30 and more minutes per week of my life looking for the source of an error!?

    Have you seen https://github.com/tomarrell/wrapcheck? It's a linter than does a fairly good job of warning when an error originates from an external package but hasn't been wrapped in your codebase to make it unique or stacktraced. It comes with https://github.com/golangci/golangci-lint and can even be made part of your in-editor LSP diagnostics.

    But still, it's not perfect. And so I remain convinced that I'm misunderstanding something fundamental about the language because not being able to consistently find the source of an error is such an egregious failing for a programming language.

  • Wrapcheck v2.3.0 released: Ignore package signatures
    2 projects | /r/golang | 3 Aug 2021
    If you're curious to read more, you can have a read here: https://blog.tomarrell.com/post/introducing_wrapcheck_linter_for_go

Stats

Basic wrapcheck repo stats
3
327
4.4
about 24 hours ago

Sponsored
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai

Did you know that Go is
the 4th most popular programming language
based on number of references?