From f11a6ae3aa36776dfde0631094fbf5b9ef1ae029 Mon Sep 17 00:00:00 2001 From: Dennis Doomen Date: Wed, 25 Mar 2026 07:11:59 -0700 Subject: [PATCH] Update AV1708 guideline Split from #298. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- _rules/1708.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/1708.md b/_rules/1708.md index e9c7f6b5..10189f97 100644 --- a/_rules/1708.md +++ b/_rules/1708.md @@ -4,7 +4,7 @@ rule_category: naming-conventions title: Name types using nouns, noun phrases or adjective phrases severity: 2 --- -For example, the name IComponent uses a descriptive noun, ICustomAttributeProvider uses a noun phrase and IPersistable uses an adjective. +For example, the name `IComponent` uses a descriptive noun, `ICustomAttributeProvider` uses a noun phrase and `IPersistable` uses an adjective. 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). 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 [{{ site.default_rule_prefix }}1008](/member-design-guidelines#{{ site.default_rule_prefix }}1008)).