Gilles Querret

Current version only computes cyclomatic complexity (number of different paths to be tested), but not cognitive complexity (understandability of code). Which one are you interested in ? The rule itself...

That will be for you @spazzymoto if you work on the new version of ABLDuck

The best would be to have a "Where used" functionality in the IDE ! But that's a good rule idea too. As Peter said, can be done for private methods....

Will be included in next release

The ABLDuck task has been provided by @spazzymoto, based on the output of the PSC code parser (already used by Mike's documentation). There's already a discussion [here](https://github.com/Riverside-Software/pct/discussions/461) about the JsonDocumentation...

Due to the current state of the parser, it won't be possible to do that for classes in assemblies. But this can be done (with a bit of changes during...

A very simplified version of the execution tree has been created for the security rules, but it's far from complete. Improving it is on the roadmap (many rules would be...

We'll add that to the backlog, but with low priority.

Is there any Progress documentation or KB entry on that ?

First part fixed in develop