-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update style cop #480
Update style cop #480
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #480 +/- ##
==========================================
- Coverage 95.00% 94.99% -0.01%
==========================================
Files 246 247 +1
Lines 10367 10367
Branches 1478 1478
==========================================
- Hits 9849 9848 -1
Misses 398 398
- Partials 120 121 +1 ☔ View full report in Codecov by Sentry. |
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.
Awesome, thanks!
Summary of Changes
This pull request updates StyleCop.Analyzers to version
1.2.0-beta.556
in the following projects:The update to the beta version is necessary to support modern C# syntax, including nullable reference types and other new language features that are not recognized by earlier stable versions of StyleCop.
Key Changes:
StyleCop Update:
1.2.0-beta.556
, which includes support for modern C# syntax.?[]
(nullable arrays), default interface implementations, pattern matching enhancements, and more.1.2.0-beta
version is now compatible with newer syntax and is essential for maintaining consistent coding style across projects using modern C#.Warning Fixes:
Why the Large PR?
I apologize for the large size of this pull request, but I opted for a fix-and-build approach. After updating StyleCop, I performed multiple fixes across all projects to ensure that the solution would build successfully and pass StyleCop analysis without any warnings.
Next Steps
Resolves issue #475