This repository was archived by the owner on Jun 5, 2025. It is now read-only.
Add rules for local field names #3215
Merged
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
dhoehna
approved these changes
Jun 13, 2024
krschau
force-pushed
the
user/krschau/rules
branch
from
47cbb85 to
081f673
Compare
AmelBawa-msft
approved these changes
Jun 14, 2024
This was referenced Jun 18, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary of the pull request
Update .editorconfig to require underscore prefixes and camelCase for local fields, except local const fields which require no prefix and PascalCase. This is already the formatting for the majority of Dev Home, the rules just codify it.
Remove duplicate rule for csharp_style_var_for_built_in_types, only use suggestion.
Update some PI code to use new rules.
References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist