Use .NoError() instead of .Nil() for error checking in tests #1566
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.
Noticed this while working on my other PR.
.NoError()
is the more correct function, as it actually prints the error instead of just saying it should've beennil
, with an ugly pointer address to a string.I made this change with a regex find/replace. It was rather specific, so there shouldn't have been any lines changed by mistake (and I didn't notice any when looking at the diff), but it's possible I missed some lines that should've been changed.