NDepend User Voice
Welcome to the NDepend User Voice page. Let us know what you would like to see in future versions of NDepend. This site is for suggestions and ideas. If you need to report a bug, please send us an email at support@ndepend.com
We look forward to hearing from you!
Thanks – Patrick Smacchia
NDepend Team
3 results found
-
Allow Implements to take a variable
It would be great to enable IType.Implement to allow passing an IType.Name instead of a string literal. That way this query would actually be possible where I am trying to get all classes that implement all interfaces. I can then check for unused interfaces.
let deps = new Func<IType, IEnumerable<IType>>(
t => from c in Types where c.Implement(t.FullName) select c
)let allInterfaces = (from t in Types
where t.IsInterface
&& (t.IsPublic || t.IsInternal)
select t)from t in allInterfaces
let dependencies = deps(t)
select new { t, dependencies}1 vote -
Let queries pull data from other queries
Logically, parts of queries can be shared between queries. For example, both "Types that could have a lower visibility" and "Potentially dead Types" need to ignore classes with only const fields. I would like queries to be able to build on the results of other queries, much as C# methods reduce code duplication by using other methods.
12 votes -
Add possibility to create CQL Rules about method parameters and variable naming conventions
Make it possible to create a rule about method parameters & variable names.
It does not seem to be supported now.3 votesActually NDepend doesn’t gather parameters & variable names at analysis time, thus such rule cannot be written with CQLinq.
- Don't see your idea?