Avoid prefixing type name with parent namespace name
Warns when the parent namespace name prefixes a contained type name (e.g. "RuntimeEnvironment" in namespace "Foo.Runtime" should be "Environment"): redundant naming without readability improvement. Types are not matched when several of them would end up with the same name once the prefix is removed (e.g. "MetricInfo" and "QualityGateInfo" both becoming "Info"). This rule doesn't warn about situations where two or more types end up with the same name.
How to fix
Remove the prefix from the type name.
CQLinq source
This rule is written in CQLinq, C# LINQ over the NDepend code model. It ships with every new NDepend project: you can read it, adapt it, or use it as a starting point for your own custom rules.
// <Name>Avoid prefixing type name with parent namespace name</Name>
// <Id>ND2013:AvoidPrefixingTypeNameWithParentNamespaceName</Id>
warnif count > 0
// Candidate types whose name starts with the parent namespace
// name, followed by an upper-case letter. This way we avoid
// matching false-positive where namespace name is "Stat" and
// type name is "Statistic".
let candidates = (
from t in JustMyCode.Types
where !t.IsNested &&
!t.IsGeneratedByCompiler
let ns = t.ParentNamespace.SimpleName
where ns.Length > 0 &&
t.Name.Length > ns.Length &&
char.IsUpper(t.Name[ns.Length]) &&
t.Name.StartsWith(ns)
select new {
t,
namespaceName = ns,
suffix = t.Name.Substring(ns.Length)
}
).ToArray()
// Suffixes shared by several candidate types. Removing the
// prefix from all of them would end up with several types
// sharing the same name (e.g. MetricInfo and QualityGateInfo
// would both become Info). Don't warn in this situation.
let ambiguousSuffixes = candidates
.GroupBy(c => c.suffix)
.Where(g => g.Count() > 1)
.Select(g => g.Key)
.ToHashSetEx()
from c in candidates
where !ambiguousSuffixes.Contains(c.suffix)
select new {
c.t,
c.namespaceName,
Debt = 10.ToMinutes().ToDebt(),
Severity = Severity.Medium
}
//<Expl>
// The *{0}'s name* starts with the parent namespace name *{1}*.
// This results in redundant naming without any improvement in
// readability.
//</Expl>
//<Desc>
// Warns when the parent namespace name prefixes a contained type
// name (e.g. "RuntimeEnvironment" in namespace "Foo.Runtime"
// should be "Environment"): redundant naming without readability
// improvement. Types are not matched when several of them would
// end up with the same name once the prefix is removed (e.g.
// "MetricInfo" and "QualityGateInfo" both becoming "Info").
// This rule doesn't warn about situations where two or more
// types end up with the same name.
//</Desc>
//<HowToFix>
// Remove the prefix from the type name.
//</HowToFix>
Open in the interactive Rules Explorer · All default rules
Naming Conventions: all 23 items
- Instance fields naming convention ND2000
- Static fields naming convention ND2001
- Interface name should begin with a 'I' ND2002
- Abstract base class should be suffixed with 'Base' ND2003
- Exception class name should be suffixed with 'Exception' ND2004
- Attribute class name should be suffixed with 'Attribute' ND2005
- Types name should begin with an Upper character ND2006
- Methods name should begin with an Upper character ND2007
- Do not name enum values 'Reserved' ND2008
- Avoid types with name too long ND2009
- Avoid methods with name too long ND2010
- Avoid fields with name too long ND2011
- Avoid having different types with same name ND2012
- Avoid prefixing type name with parent namespace name ND2013
- Avoid naming types and namespaces with the same identifier ND2014
- Don't call your method Dispose ND2015
- Methods prefixed with 'Try' should return a boolean ND2016
- Properties and fields that represent a collection of items should be named Items. ND2017
- DDD ubiquitous language check ND2018
- Avoid fields with same name in class hierarchy ND2019
- Avoid various capitalizations for method name ND2020
- Controller class name should be suffixed with 'Controller' ND2021
- Nested class members should not mask outer class' static members ND2022