-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Turn on some CodeAnalysis rules #32837
Conversation
src/HttpClientFactory/Polly/src/HttpRequestMessageExtensions.cs
Outdated
Show resolved
Hide resolved
16511e0
to
e89535e
Compare
🆙 📅 |
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.
I've skimmed through this and can't spot anything to get worried about. All looks good!
One aspect that I'm slightly unsure about is removing unused things that seem to relate to external specifications (e.g., the lists of "libs" in UnsafeNativeMethods.cs, or the things in H2SpecCommands.cs). Arguably there's value in representing the full list to avoid confusion about what the missing values are. However since none of that is code that I have a lot of close expertise with, assuming the code owner is happy then I'm sure it's fine!
@Tratcher the changes @SteveSandersonMS is talking about are largely in http.sys and IIS's sources. Could you have a look and let me know what your recommendation is? |
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 UnsafeNclNativeMethods cleanup is fine. The h2spec consts I would keep only if it were product code, but this is a test tool that I don't expect to modify.
* Turn on some CodeAnalysis rules Commit migrated from dotnet/aspnetcore@af9bb41d623b
Contributes to #24055
Going thru https://github.com/dotnet/runtime/blob/main/eng/CodeAnalysis.ruleset and adding the ones that have been enabled in that repo.