Stone_Red/naming-convention
1
0
Fork 0
mirror of https://github.com/Stone-Red-Code/naming-convention.git synced 2026-09-08 07:56:10 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #28 from OJacot-Descombes/master

Browse Source 
Further clarified C# item #7 about casing of abbreviations.
This commit is contained in:
Konstantin
2020-08-20 22:28:07 +03:00
committed by GitHub
parent b07f1005e9 64950ee66d
commit d32928107f
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
C# Coding Standards and Naming Conventions.md
+4 -3
View File
@@ -99,12 +99,13 @@ UriPart uriPart;
***Why: consistent with the Microsoft's .NET Framework and prevents inconsistent abbreviations.*** ***Why: consistent with the Microsoft's .NET Framework and prevents inconsistent abbreviations.***
#### 7. Do use camelCasing for abbreviations 3 characters or more (2 chars are both uppercase):
#### 7. Do use PascalCasing or camelCasing (Depending on the identifier type) for abbreviations 3 characters or more (2 chars are both uppercase when PascalCasing is appropriate or inside the identifier).:
```csharp ```csharp
HtmlHelper htmlHelper; HtmlHelper htmlHelper;
FtpTransfer ftpTransfer; FtpTransfer ftpTransfer, fastFtpTransfer;
UIControl uiControl; UIControl uiControl, nextUIControl;
``` ```
***Why: consistent with the Microsoft's .NET Framework. Caps would grab visually too much attention.*** ***Why: consistent with the Microsoft's .NET Framework. Caps would grab visually too much attention.***