I am grateful for the assess_size_codebase assessment. In addition to that, would it be possible to implement an assessment of cyclomatic complexity?
An implementation of the is already available in the codebase of the lintr package:
https://lintr.r-lib.org/reference/cyclocomp_linter.html
For me, the cyclomatic complexity of a package is as relevant as the volume of its codebase. For example, if I want to calculate the average of a metric between a package and its dependencies (see my recent work for the Validated R Repository Working Group, I might want some of these average calculations to be weighted by the cyclomatic complexity of each package.
I am grateful for the
assess_size_codebaseassessment. In addition to that, would it be possible to implement an assessment of cyclomatic complexity?An implementation of the is already available in the codebase of the
lintrpackage:https://lintr.r-lib.org/reference/cyclocomp_linter.html
For me, the cyclomatic complexity of a package is as relevant as the volume of its codebase. For example, if I want to calculate the average of a metric between a package and its dependencies (see my recent work for the Validated R Repository Working Group, I might want some of these average calculations to be weighted by the cyclomatic complexity of each package.