Methods prefixed with 'Try' should return a boolean
A method prefixed with Try is expected to return a boolean (or Task<bool> if async) reflecting success or failure, usually with the result in an out parameter, e.g. System.Int32.TryParse(int,out string):bool
How to fix
Rename the method, or transform it into an operation that can fail.
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>Methods prefixed with 'Try' should return a boolean</Name>
// <Id>ND2016:MethodsPrefixedWithTryShouldReturnABoolean</Id>
warnif count > 0
from m in Application.Methods where
m.SimpleNameLike("^Try") &&
m.ReturnType != null &&
// Accept boolean or value tuple (eventually nullable) as return type
!m.ReturnType.FullNameEqualsAny("System.Boolean","System.Nullable<T>") &&
m.ReturnType.SimpleName != "ValueTuple" &&
!m.ReturnType.Name.Contains("Task")
select new {
m,
m.ReturnType,
Debt = 10.ToMinutes().ToDebt(),
Severity = Severity.Medium
}
//<Expl>
// The *{0}* returns the *{1}*.
// Usually a method whose name starts with *Try* returns a *bool* value
// to allow client code to test whether its execution succeeded or not.
//</Expl>
//<Desc>
// A method prefixed with **Try** is expected to return a *boolean* (or
// *Task<bool>* if async) reflecting *success* or *failure*, usually with
// the result in an *out parameter*, e.g.
// *System.Int32.TryParse(int,out string):bool*
//</Desc>
//<HowToFix>
// Rename the method, or transform it into an operation that can fail.
//</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