Code Cleanup | Fixing Inconsistent Modifiers#2765
Code Cleanup | Fixing Inconsistent Modifiers#2765benrr101 wants to merge 2 commits intodotnet:mainfrom
Conversation
|
I like your changes, but this is going to cause me a lot of pain when we have to bring in the JSON changes from the feature branch, after the protocol changes are published |
|
For this kind of code style change, I'd highly recommend encoding the applied style in .editorconfig, so that discrepancies don't creep back in in the future. |
|
Please hold off on the merge of this PR till we drive #2714 and JSON work to conclusion. |
|
@saurabh500 I think, we can also have RoslynAnalyzer to enforce some coding standards to prevent this in future as this cannot be done in editorconfig file. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2765 +/- ##
==========================================
+ Coverage 71.70% 71.73% +0.02%
==========================================
Files 308 308
Lines 62314 62314
==========================================
+ Hits 44682 44698 +16
+ Misses 17632 17616 -16
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@roji Ok, I've added it to the editorconfig at the root of the repo |
|
@benrr101 can you please resolve these conflicts? |
|
Closing as too many things have changed since last working on this. BUT I HAVEN'T GIVEN UP 😤 |
Description: One thing that lights up my IDE a lot is inconsistent ordering of modifiers for methods, properties, etc. This PR does a quick sweep of the codebase (automated) and reorders the modifiers to be consistent with C# standards.
AI Analysis:

Testing: Well ... if it builds and passes the CI tests, I think it's good to go.