Skip to content

Update coding guidelines for control statement formatting #6904

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.

Sign up for GitHub

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

Closed
Nigusu-Allehu wants to merge 2 commits into from
Closed

Update coding guidelines for control statement formatting #6904

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
54646e1
Update coding guidelines for control statement formatting
Nigusu-Allehu Oct 27, 2025
7e91d74
Less strict
Nigusu-Allehu Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/coding-guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,25 @@ The general rule we follow is "use Visual Studio defaults".

1. Avoid more than one empty line at any time. For example, do not have two blank lines between members of a type.

1. Add a blank line before control statements such as `if`, `for`, and `while` loops.
For readability, ensure there is a space ahead of these statements. For example:

```csharp
statement1
statement2

if (...)
{
}

// Not:
statement1
statement2
if (...)
{
}
```

1. Avoid lines of code longer than 120 characters.

1. Avoid spurious free spaces. For example avoid `if (someVar == 0)...`, where the dots mark the spurious free spaces. Consider enabling "View White Space (Ctrl+R, Ctrl+W)" or "Edit -> Advanced -> View White Space" if using Visual Studio to aid detection.
Expand Down