Skip to content
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 'Use proper Assert methods' analyzer #4052

Merged
merged 3 commits into from
Nov 15, 2024

Conversation

Youssef1313
Copy link
Member

Implements the analyzer part of #3315. Codefix isn't yet implemented.

Copy link
Member

@Evangelink Evangelink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work @Youssef1313

@Evangelink Evangelink merged commit 6749aa3 into microsoft:main Nov 15, 2024
7 checks passed
Comment on lines +65 to +66
DiagnosticSeverity.Info,
isEnabledByDefault: false);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Evangelink I just remembered that we haven't discussed this. Is the current severity and being not enabled by default okay? Or should it be enabled by default?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can enable by default, I am only careful about the warning severity and outside of breaking change version I try to set it as warning only for rules where failure to comply would result in runtime error as we have many users with warn as error who would get broken by bumping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants