-
Notifications
You must be signed in to change notification settings - Fork 465
Issues: dotnet/roslyn-analyzers
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Struct constructor with only optional parameters not used
Area-Microsoft.CodeAnalysis.NetAnalyzers
Category-Design
Rules supporting .NET Framework Design Guidelines
untriaged
#7179
opened Feb 4, 2024 by
bjornhellander
Do not flag for CA1056 on members decorated as Rules supporting .NET Framework Design Guidelines
Need More Info
[DataMember]
Area-Microsoft.CodeAnalysis.NetAnalyzers
Category-Design
CA1002: Return part: only for virtual members - or better description
Category-Design
Rules supporting .NET Framework Design Guidelines
False_Positive
A diagnostic is reported for non-problematic case
Needs-Review
Prevent breaking design change diagnostic on public API members
Category-Design
Rules supporting .NET Framework Design Guidelines
Feature Request
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Update Dispose pattern rule to handle DisposeAsync pattern
Category-Design
Rules supporting .NET Framework Design Guidelines
Feature Request
Needs-Review
Add an analyzer to require optional parameters be specified for internal invocations
Approved-Rule
Indicates if the new proposed rule has been approved to move to implementation phase
Area-Microsoft.CodeAnalysis.NetAnalyzers
Category-Design
Rules supporting .NET Framework Design Guidelines
Feature Request
help wanted
The issue is up-for-grabs, and can be claimed by commenting
ProTip!
What’s not been updated in a month: updated:<2024-09-20.