Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow members that could be private to not be #10

Open
phiresky opened this issue Nov 28, 2022 · 0 comments · May be fixed by #11
Open

Allow members that could be private to not be #10

phiresky opened this issue Nov 28, 2022 · 0 comments · May be fixed by #11

Comments

@phiresky
Copy link

This is a really useful project!

It would be great if it was possible to ignore all the "should be private" errors and only show those that are not used at all. Depending on the code base the "should be private" messages seem mostly noise, while the "completely unused" messages are really useful.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add flag to ignore members that are public but could be private phiresky/ts-unused-class-members
1 participant
@phiresky