Reformat TypePreinit.cs #115191
Merged
Reformat TypePreinit.cs #115191
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VS changed its mind how this should be formatted (or we added `.editorconfig` that does that at some point?) and when editing this file I find myself constantly struggling with where VS wants spaces. I don't like reformatting, but don't see a way out - it affects the entire big switch block.
ghost
added
the
Contributor
There was a problem hiding this comment.
Pull Request Overview
This pull request reformats the file TypePreinit.cs to improve consistency in code style and indentation according to the updated Visual Studio/.editorconfig settings. The key changes include the consistent use of braces around code blocks, standardizing switch-case block formatting, and minor whitespace adjustments across the file.
Contributor
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
jkotas
approved these changes
Apr 30, 2025
Member
|
/ba-g build analysis stuck |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
VS changed its mind how this should be formatted (or we added
.editorconfigthat does that at some point?) and when editing this file I find myself constantly struggling with where VS wants spaces. I don't like reformatting, but don't see a way out - it affects the entire big switch block.