This repository was archived by the owner on Dec 1, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't know about the discussions but I like the API additions, so I took a stab at adding some tests.
Adds
testFormatCompleteCompare
as additional testing func. The new function takes a string slice aswant
, wherein stacktraces and non-stacktrace messages are discerned bystrings.ContainsAny(want[i], "\n")
. For example usage, seeTestFormatWithStack
&TestFormatWithMessage
.#76 I do not understand the third todo, I thought causer and stack-tracer are separate interfaces so I'm a little bit confused. Is it supposed to add
NearestCauseWithStackTrace()
or some similar function?