We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, if you use a library that outputs wrapped errors, you end up with duplicates.
For example:
Results in:
errorf wrapped: stdlib sentinel error: stdlib sentinel error
The stdlib sentinel error part is duplicated, which is just noise when trying to read errors.
stdlib sentinel error
Solution? Not sure what the best course of action is, but it seems fairly simple to just use the next error message to de-duplicate/split the current.
For example, given:
[1] errorf wrapped: stdlib sentinel error [2] stdlib sentinel error
errorf wrapped: stdlib sentinel error
When processing [1], look ahead to [2] and remove [2]'s nested message from [1], so we're left with:
[1] errorf wrapped [2] stdlib sentinel error
errorf wrapped
The text was updated successfully, but these errors were encountered:
More cleverly split up glued error messages #24
6fcb71b
a79d295
No branches or pull requests
Currently, if you use a library that outputs wrapped errors, you end up with duplicates.
For example:
Results in:
The
stdlib sentinel error
part is duplicated, which is just noise when trying to read errors.Solution? Not sure what the best course of action is, but it seems fairly simple to just use the next error message to de-duplicate/split the current.
For example, given:
[1]
errorf wrapped: stdlib sentinel error
[2]
stdlib sentinel error
When processing [1], look ahead to [2] and remove [2]'s nested message from [1], so we're left with:
[1]
errorf wrapped
[2]
stdlib sentinel error
The text was updated successfully, but these errors were encountered: