Added a combination of formatting/stylecheck tools for style parity with Java#151
Merged
Conversation
…in spirit, with some specifics modified for .NET conventions) with Java, and fixed all the pre-existing violations
mikeb01
reviewed
May 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
"style parity" is largely in spirit, not exact; where there are longstanding .NET code or naming conventions recommended by Microsoft and most .NET projects, those naming and coding conventions are enforced instead even if they deviate a bit from Java.
There should not be any public behavior changes in this review other than at build-time (lots of new build-time style errors now). The vast majority of the changes are whitespace / formatting / line wrapping changes.