You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While writing some tests with errtrace, I had a scenario where the formatted error didn't have an error trace, even though underlying errors were wrapped.
Although we may want to simplify the output first too #74.
I think the tree-format is more trouble than it's worth.
I doubt anybody finds that useful over just empty-line or --- separated traces.
While writing some tests with errtrace, I had a scenario where the formatted error didn't have an error trace, even though underlying errors were wrapped.
Example snippet,
gives:
Since the last error was not wrapped with errtrace, the
%+v
has no impact. However,FormatString
does work correctly in this case.While we can't fix this, is this gotcha worth calling out somewhere, and should we recommend
errtrace.FormatString
over%+v
.The text was updated successfully, but these errors were encountered: