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
Currently we use go-cmp for non-test code in some verification logic. Since go-cmp is meant to be used in tests, I think we should avoid using it in non-test code.
The text was updated successfully, but these errors were encountered:
Previously we used the go-cmp's Diff for displaying a human-friendly diff between two structs in an error message.
I had intended to do a json print of the structs and do a line-by-line diff. There is an internal library for calculating text diff, but I don't see any external functions that expose it:
https://pkg.go.dev/golang.org/x/tools/internal/diff
Instead, this we will simply display both structs in their own "actual" and "expected" sections. The user can use their other tools to find a human-friendly diff.
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
…ramework#737)
Previously we used the go-cmp's Diff for displaying a human-friendly
diff between two structs in an error message.
I had intended to do a json print of the structs and do a line-by-line
diff. There is an internal library for calculating text diff, but I
don't see any external functions that expose it to make it available for
our use: https://pkg.go.dev/golang.org/x/tools/internal/diff
Instead, this we will simply display both structs in their own "actual"
and "expected" sections. The user can use their other tools to find a
human-friendly diff.
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Currently we use go-cmp for non-test code in some verification logic. Since go-cmp is meant to be used in tests, I think we should avoid using it in non-test code.
The text was updated successfully, but these errors were encountered: