testing: compare Rule types and ignore struct fields #740
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.
As observed in #738,
AssertIssues
was not comparing the rule in an issue. Purely removingIgnoreFields
is not an option because it causes panics due to unexported fields:Panic output
IgnoreUnexported
doesn't work because every rule is its own struct and we have to pass struct values. Not to mention it doesn't fit the intent here.In usage,
AssertIssues
is just being used with matching rule types and not with equal values. This implements a custom comparer that performs that check, considering twoRule
interfaces equal if they both have the same concrete type.