-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(eslint-plugin): [no-unused-private-class-members] new extension rule #10913
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks for the PR, @bradzacher! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit f7beddc
☁️ Nx Cloud last updated this comment at |
|
View your CI Pipeline Execution ↗ for commit 34b77b8. ☁️ Nx Cloud last updated this comment at |
JoshuaKGoldberg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
packages/eslint-plugin/src/rules/no-unused-private-class-members.ts
Outdated
Show resolved
Hide resolved
packages/eslint-plugin/src/rules/no-unused-private-class-members.ts
Outdated
Show resolved
Hide resolved
| // mark the first member we encounter as used. If you were to delete the | ||
| // member, then any subsequent usage could incorrectly mark the member of | ||
| // an encapsulating parent class as used, which is incorrect. | ||
| trackedClassMembersUsed.add(memberDefinition.declaredNode); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Bug]: I've noticed some missed reports with functions that have a different this than the class instance (deploy preview playground link):
class Test1 {
// should be reported but doesn't?
private bar: number;
foo = function () {
return this.bar;
}
}There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is because the base rule doesn't support that case because this.#bar is a syntax error inside a function expression!!
It's worth noting that TS doesn't actually catch this case either and reports bar as unused because the type of the this in the function expression is any!
If you turn on noImplicitThis then TS will error on that this
We could support this if we wanted to. I'm leaning towards not because TS itself doesn't catch it either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! I think the rule should report bar as unused in this case. I've mentioned this since TypeScript reports it as unused but the rule doesn't report it as unused (regardless of the type error).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coming back to this -- my code handles this correctly because realistically it is an actual usage of the parameter.
For example new Test1().foo() will return the value of bar.
There's an implicit binding here and so I think this is fine to keep not reporting on.
packages/eslint-plugin/src/rules/no-unused-private-class-members.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks amazing! Excited to enable this on projects I work on 🚀🚀🚀
(I accidentally posted the review earlier while still adding comments 🙈)
|
FYI I'm going to make @Josh-Cena very happy - I'm going to build a "class scope analyser" so we can do this right rather than just hacking it in. This does mean that I'm going to rewrite the rule from the ground up -- but it'll be worht it |
Do you intend for this to proceed as-is, with this work intended to happen in the future, or should we pause/draft it pending this work? |
|
Let's draft it. |
ronami
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks amazing and a very beneficial rule to have; just a few small comments from me 🚀🚀🚀
packages/eslint-plugin/src/util/class-scope-analyzer/classScopeAnalyzer.ts
Show resolved
Hide resolved
packages/eslint-plugin/src/util/class-scope-analyzer/classScopeAnalyzer.ts
Outdated
Show resolved
Hide resolved
| meta: { | ||
| type: 'problem', | ||
| docs: { | ||
| description: 'Disallow unused private class members', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a bug and shouldn't be reported (deploy preview playground link):
class Test1 {
// reported but shouldn't?
private foo: number | null;
public bar() {
this.foo ??= 1;
}
}There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a weird case that isn't currently reported by no-unused-vars but really should be.
It is reported by the base no-unused-private-class-members rule
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was just a recent eslint bug report about these; I guess it's intentional for no-unused-vars since x ?? = y reads x first (equivalent to x != null ? x : (x = y)) rather than unconditionally assigning (x = x != null ? x : y). See eslint/eslint#20029. But presumably the two rules should agree?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, but do note that these are reported by no-useless-assignment so 🤷♂️ 🤷♂️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably file a bug for NUPCM then so it matches NUV?
JoshuaKGoldberg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have very little to add that Kirk and Ronami didn't already. Very exciting!! ⚡
packages/eslint-plugin/src/util/class-scope-analyzer/extractComputedName.ts
Outdated
Show resolved
Hide resolved
| */ | ||
| export function extractNameForMember(node: MemberNode): [Key, string] | null { | ||
| if (node.computed) { | ||
| return extractComputedName(node.key); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noting, #11006 has some other logic around computed keys. It might be useful to unify?
|
@ronami / @JoshuaKGoldberg / @kirkwaiblinger Added support for: Parameter properties class Test1 {
constructor(
// errors
private parameterPropertyUnused: number,
// no error
private parameterPropertyUsed: number,
) {}
method() {
return this.parameterPropertyUsed;
}
}Usage of a private class member via explicitly and simply annotated variables: class Foo {
// no longer reported
private prop: number;
// no longer reported
private staticProp: number;
method1(thing: Foo) {
return thing.prop;
}
method2(thing: typeof Foo) {
return thing.staticProp;
}
}Usage of a private class member via simple assignment: class Foo {
// no longer reported
private prop: number;
method() {
const self = this;
return self.prop;
}
} |
JoshuaKGoldberg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lint complaints notwithstanding, this looks great to me! I'll defer to the other reviewers on the finer points they're calling out. But the overall scope analyzer looks great and I'm very happy with the clean rule implementation. Nicely done! 👏
ronami
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great 👏👏👏
2ccb638
408410c to
2ccb638
Compare
Codecov Report❌ Patch coverage is ❌ Your patch status has failed because the patch coverage (82.10%) is below the target coverage (90.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #10913 +/- ##
==========================================
- Coverage 90.66% 90.56% -0.10%
==========================================
Files 518 522 +4
Lines 52454 53063 +609
Branches 8694 8838 +144
==========================================
+ Hits 47558 48058 +500
- Misses 4882 4990 +108
- Partials 14 15 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|


PR Checklist
Overview
This PR implements an extension rule for
no-unused-private-class-membersthat introduces support forprivatemembers.