Show unused public properties and methods

[jabacchetta]

It would be nice to have unused detection expanded, capable of detecting unused methods, exports, etc.

Code Example

Shape.js

class Shape {
 constructor() {
 this.color = 'red';
 }

 colorLog() {
 console.log(this.color);
 }
}

export default Shape;

Circle.js

import Shape from "./Shape";

class Circle extends Shape {
 constructor() {
 super();

 // FIXME: description should show as unused in VSCode, as it does in WebStorm.
 this.description = 'A circle shape';
 }

 // FIXME: circleLog should show as unused in VSCode, as it does in WebStorm.
 circleLog() {
 // NOTE: both VSCode and WebStorm have detected an unused variable.
 const num = 2;

 // NOTE: colorLog is being used, so no unused code errors in Shape.js file.
 super.colorLog();
 }
}

// FIXME: export should show as unused in VSCode, as it does in WebStorm.
export default Circle;

VSCode Screen

WebStorm Screen

[mjbvz]

We currently assume that exported members form a public API and therefore are always used. We could try to detect that a certain set of files are an API entrypoints, and then mark unused internal exports. Not sure if there are any issue already tracking this

[auchenberg]

Customer demand for this feature mentioned in https://dev.to/mokkapps/why-i-switched-from-visual-studio-code-to-jetbrains-webstorm-939.

[zpdDG4gta8XKpMCd]

what about exported but unused

• modules
• classes
• types
• interfaces/props
• members (enum | union)
• functions
• constants/variables?