Tech Debt Metrics (dormant)

https://vuejs.org/guide/scaling-up/sfc.html

When my code is scored, I want to be able to control the scoring mechanism simply by changing numbers or turning nobs for the algorithm to understand to ease or be more strict in evaluations. Use-case: New project, rapid development, and prototyping -- I want to be able to relax the critical nature of the algo because we are alright with some dirtiness.

Currently, the whole React component is seen is one excessively large function which always gets a bad rating. It'd be good to have the React component treated separately or at least have the individual functions within the React component assessed separately. Thanks.

A summary page that lists out the worst offenders of tech debt in a repository. Would certainly help with large angular monorepos

Allowing the extension to work with Microsoft DevOps would be great.

The extension's team features (impact / effort voting & notes on improvements) only work in single-root workspaces (i.e. just one git repo open). Support multiroot workspaces for users working on multiple git repos in one window.

Please add support for es6 arrow functions.

A seperate view with a complete list of all the tech debt ratings in the product would help tremendously to identify weakpoints. Maybe even a tech debt rating for a file consisting of the average of the complete resulting tech debt in that file.

One should be able to sort the list of dept by rating. When one wants to fix tech debt one probably wants rating E on the top.

Years ago I found a fantastic metric implemented by mixing cyclomatic complexity + code coverage. (crap4j) It feels like it might be targetting the same thing your tool it aiming at. And it generally yielded better code by trying to improve that metric. https://blog.ndepend.com/crap-metric-thing-tells-risk-code/