Closed Halleck45 closed 6 months ago
The recent updates introduce enhancements in complexity analysis and risk assessment within a code analysis tool. New logic calculates the sum of complexity metrics for better file complexity analysis and introduces cyclomatic complexity calculation for non-object-oriented languages. Risk analysis now differentiates between procedural and OOP files, using maximum cyclomatic complexity for more nuanced risk scoring. Additionally, user interface improvements were made for file name display, and a method was renamed for consistency in the Golang engine, affecting both its usage and tests.
Files | Summary |
---|---|
src/Analyzer/Aggregator.go |
Added logic to calculate the sum of complexity metrics for functions in a file. |
src/Analyzer/Complexity/CyclomaticVisitor_test.go , src/Engine/Golang/GolangRunner.go , src/Engine/Golang/GolangRunner_test.go |
Added cyclomatic complexity calculation for non-OOP languages and renamed parseGoFile to ParseGoFile affecting invocation and tests. |
src/Analyzer/RiskAnalyzer.go |
Introduced calculation of maxCyclomatic and adjusted risk scoring based on complexity metrics for different file types. |
src/Cli/ComponentFileTable.go |
Modified file name handling in the UI to truncate long filenames. |
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Summary by CodeRabbit