-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
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
Implement codefix for MSTEST0037: Use proper 'Assert' methods #4162
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the cases leading to compilation error, could we tweak the rule not to report instead?
@@ -354,10 +582,28 @@ public void MyTestMethod() | |||
} | |||
"""; | |||
|
|||
await VerifyCS.VerifyAnalyzerAsync( | |||
// error CS1503: Argument 1: cannot convert from 'object' to 'bool' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we instead not raise? We could detect if that can be converted to the other type. I guess
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The diagnostic is still correct IMO. It's that the codefix should be producing a cast.
@@ -397,10 +646,28 @@ public void MyTestMethod() | |||
} | |||
"""; | |||
|
|||
await VerifyCS.VerifyAnalyzerAsync( | |||
// error CS1503: Argument 1: cannot convert from 'object' to 'bool' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same remark about avoiding the analyzer diagnostic instead.
Fixes #3315