-
Notifications
You must be signed in to change notification settings - Fork 507
Issues: DotNetAnalyzers/StyleCopAnalyzers
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
AD0001 in many analyzers when stylecop.json link is broken
#3902
opened Nov 17, 2024 by
bjornhellander
SA1008 false positive on range expression with first operand in parentheses
#3894
opened Oct 16, 2024 by
rotanov
New rule proposal: Do not use nullable variables in arithmetic
#3891
opened Sep 18, 2024 by
b-jeltes-tjip
New rule proposal: Declare precedence when using null-coalescing operators
#3890
opened Sep 17, 2024 by
b-jeltes-tjip
SA1600 fires for internal interfaces even if documentInternalElements is false
#3888
opened Sep 2, 2024 by
ds1709
SA1200 (Using directives must be placed correctly) is firing in file with only global usings
#3875
opened Jul 11, 2024 by
bjornhellander
SA1649 code fix (rename file) copies linked files into all referencing projects
#3866
opened Jun 29, 2024 by
bjornhellander
SA1514 is falsely reported when documenting types declared in the global namespace
bug
up for grabs
#3849
opened May 28, 2024 by
Arthri
Do not warn SA1001 (Commas should be spaced correctly) if comma follows a preprocessor directive
bug
up for grabs
#3816
opened Mar 9, 2024 by
mikernet
Previous Next
ProTip!
Updated in the last three days: updated:>2024-11-16.