Why do these metrics matter? What should I do to improve my code when a given metric is red?
We're planning to do this in the near future, although it's not our immediate focus.
Maybe display in the "inspect function" view what metrics is looking for. For example when "length is green". I'd want to be able to see why. I'd love to be able to see how much longer I can make my function before that metrics turns orange. Something like "11 lines left", or "38 lines over" in case it's red.
I've seen your short term roadmap, I love the "code intelligence" section. I love the idea of showing "why" we should care about a certain metric, but I'm personally missing the "how".
Other than that, keep up the good work, amazing extension.
@Luïs De Zutter: Thank you for your input! That makes total sense, and matches up with other feedback we've received 🙌
We need to update the Code Intelligence wireframes to expand on the green/amber/red indicators and expose more information about the metrics.
We're currently very focused on team features to prioritise refactoring work but we'll try to get to this as soon as possible 🙏
(If anyone is wondering about the short term roadmap being referred to, you can find it here https://www.figma.com/file/h40UptSUAW9V05BtwneeiL/VSCode-Wireframe-Kit?node-id=1464%3A0 )