Support test file rating mode
mocha test files includes many describe, it,... statements nested in each other, should we rate those files differently...?
Track 'Testing' as a metric of Tech Debt
Working on a medium Angular 8 app where "shipping software" was prioritized over "shipping tested software." Most of the unit tests are either the bare-bones shell cranked out by the CLI or are skipped/commented out. E - No unit test file exists for that component. D - Only the CLI-generated spec.ts file exists. C through A - Each testable method (public with return type) has a test, each HTML element with an ID has a test, etc.
Support for React
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.
Allow metric customisation
Use default metrics, but allow us to tweak those metrics in the extension settings to our personal desire.
Integrate with Gitlab
Allow this wonderful extension to work with cloud & self-hosted gitlab versions.
Avoid Information Overload
Remove all the information developers don't necessarily need during development. i.e icon, signed in message, many recent changes banner
Complete tech debt overview of the whole open workspace
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.
Explain the metrics
Why do these metrics matter? What should I do to improve my code when a given metric is red?
Our team is working on a giant product with massive tech debt. However, we wouldn't consider function name lengths etc. really to be technical debt. For this stuff, we use TSLint/ESLint and that works quite well. What really hurts us is keeping track of DESIGN debt (mostly domain-specific): Modularization, code dependencies, ... all this things can't be tracked automatically. Is there a way to manually "add" debt for design debt, e.g. by adding a comment to the code? The other thing is that only half the people use VSCode, so a command line tool would be great as well.