fix: time.Time rendering in the diff returned by error message

[ccoVeille]

Summary

Improve formatting when dealing with time.Time now we vendored gospew

Changes

Now, go-spew is vendored, we can fix old issues we had.

We can fix the representation of time.Time in gospew

And remove the imperfect fix we had in place.

Motivation

#895 was created by @luan to solve some legitimate issues. It was released with v1.6.0 on May 29, 2020

• Disable using Stringer/error interfaces for diffing #895

But unfortunately, the changes lead to an issue with the way time.Time are rendered. So #989 was opened on Aug 1, 2020 by @AlekSi

• time.Time comparison produces non-helpful diff #989

The issue was somehow fixed with #1072 by @HaraldNordgren

• Make sure time.Time comparison produces a helpful diff. closes #989 #1072

#1072 was merged in Apr 27, 2021 (but only released in Mar 1, 2024 with v1.7.1 )

Unfortunately, the fix was incomplete, as it was working only for first level, so #1078 was opened on May 22, 2021 by @shawc71

• Diffs on structs with nested time.Time objects produce hard to read diffs #1078

#1079 was opened by @shawc71 on May 22, 2021 to try to fix the issue

• Make spew config selection configurable to allow for helpful diffs on time.Time objects nested in structs. #1079

But it was never merged, as the solution was also imperfect, and because they were no solution inside testify to fix this

So #1078 was left open until now.

Related issues

• Related to go-spew vendoring #1826
• Closes Make spew config selection configurable to allow for helpful diffs on time.Time objects nested in structs. #1079
• Closes Diffs on structs with nested time.Time objects produce hard to read diffs #1078

[ccoVeille]

@brackendawson please review, it's ready.

I'm facing this issue with testify for ages, I cannot wait to see it fixed 😬

[fredbi]

@ccoVeille I found your PR definitely interesting but perhaps lacking a few things.
You may find an alternate implementation there go-openapi#27
The main differences are:

• does not use type string representation, but type convertibility to time
• does not sort using the string representation (time.Time does NOT implement sort.Interface), but uses time.Time.Compare instead
• more tests with embedded types, private fields, pointers, nil values etc

Could be interesting to exchange our views

[ccoVeille]

Thanks @fredbi. I will take a look.

I saw the PRs you made in the last days.

I agree with you about the string sort that can lead to problem when comparing for example 999-12-31 and 1000-01-01

I'll review the PR in your fork also