Skip to content

Commit 153d1ab

Browse files
bkoelmandennisdoomen
authored andcommitted
Updated type naming examples (#84)
1 parent d3087ee commit 153d1ab

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

Src/Guidelines/1700_NamingGuidelines.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ For example, use `OnButtonClick` rather than `OnBtnClick`. Avoid single characte
5252
- Identifiers that refer to a collection type should have plural names.
5353

5454
### <a name="av1708"></a> Name types using nouns, noun phrases or adjective phrases (AV1708) ![](images/2.png)
55-
Bad examples include `SearchExamination` (a page to search for examinations), `Common` (does not end with a noun, and does not explain its purpose) and `SiteSecurity` (although the name is technically okay, it does not say anything about its purpose). Good examples include `BusinessBinder`, `SmartTextBox`, or `EditableSingleCustomer`.
55+
For example, the name IComponent uses a descriptive noun, ICustomAttributeProvider uses a noun phrase and IPersistable uses an adjective.
56+
Bad examples include `SearchExamination` (a page to search for examinations), `Common` (does not end with a noun, and does not explain its purpose) and `SiteSecurity` (although the name is technically okay, it does not say anything about its purpose).
5657

5758
Don't include terms like `Utility` or `Helper` in classes. Classes with names like that are usually static classes and are introduced without considering object-oriented principles (see also AV1008).
5859

0 commit comments

Comments
 (0)