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
The errors return should not have newline characters and should be defined as sentinel errors (either as constants or interface) so one can assert against them.
As an example of somewhere where this is being done:
returnerrors.Errorf("flatfile.parseFlatfileTag: Invalid formatting of named option '%v'\nNamed options should be in the form option=value\nValid options:%v", options, validOptions)
Tests should also assert the specific error returned.
Example of a test not checking the error message returned at all:
The errors return should not have newline characters and should be defined as sentinel errors (either as constants or interface) so one can assert against them.
As an example of somewhere where this is being done:
flatfile/ffptag.go
Line 64 in ee3c85f
Tests should also assert the specific error returned.
Example of a test not checking the error message returned at all:
flatfile/ffptag_test.go
Lines 60 to 70 in ee3c85f
The text was updated successfully, but these errors were encountered: