-
Notifications
You must be signed in to change notification settings - Fork 509
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
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
SA1217 reporting incorrect order if System.* is placed alphabetically
#3809
opened Feb 26, 2024 by
DavidArno
SA1303: Can we configure this to warn if the 1st char is _
#3793
opened Jan 31, 2024 by
TickettEnterprises
Inquiry about Adding Chinese Language Support to StyleCop.Analyzers
#3792
opened Jan 31, 2024 by
LuckyMiku
SA1600 is not raised for record primary constructors that are missing param tags
#3780
opened Jan 16, 2024 by
SapiensAnatis
SA1013 allows any number of spaces after list initializer
question
#3747
opened Dec 7, 2023 by
ozsvart-karoly-nx
[Question] proper way ot add stylecop.json to a multiproject solution using visual studio code.
question
#3735
opened Nov 25, 2023 by
ruimaciel
New rule: multiple conditions for an if-statement should be intended
needs discussion
proposal
#3724
opened Nov 9, 2023 by
urmel9
Analyzer proposal: prefer
or
instead of multiple case
that follow through
new rule
proposal
#3721
opened Nov 6, 2023 by
ZacharyPatten
ProTip!
Find all open issues with in progress development work with linked:pr.