Skip to content

fixed grammar regarding booleans #119

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

Merged
merged 1 commit into from
Aug 10, 2020
Merged

fixed grammar regarding booleans #119

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/coding/csharp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ This largely removes the need for readonly fields in favor of properties.
- :no_entry: AVOID: incorporating the data type into the name.
- :heavy_check_mark: DO: Use C# alias types rather than their System namespace counterparts (ie. ‘int’ instead of ‘System.Int32’)
- :heavy_check_mark: DO: Use plural names for collections
- :heavy_check_mark: DO: Make boolean names should contain Is/Are/Can/Has which implies Yes/No or True/False values.
- :heavy_check_mark: DO: Boolean names should contain Is/Are/Can/Has which implies Yes/No or True/False values.
- :no_entry: AVOID: Double negatives when referring to booleans.
- :no_entry: AVOID: var in cases where the the type of var is not obvious. Common exceptions would be constructors and generic method calls where it is clear the generic type is the return value.

Expand Down