We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Equals does no do what people might think.
See: https://community.sonarsource.com/t/fluentassertion-should-and-equals-methods-shouldnt-be-used-together/38181
The text was updated successfully, but these errors were encountered:
@Corniel hasn't this been handled in #95 ?
Sorry, something went wrong.
@Meir017 I can test that. Both ways, you should advocate there I think. :)
@Corniel that's exactly what the analyzer + code-fixer suggest here. basically never use Equals with fluent-assertions
Equals
Thanx,. I'll report that.
No branches or pull requests
Equals does no do what people might think.
See: https://community.sonarsource.com/t/fluentassertion-should-and-equals-methods-shouldnt-be-used-together/38181
The text was updated successfully, but these errors were encountered: