We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
TS6133 6133 noUnusedLocals
This is related but more general: #13408
This ts.Diagnostic message is classified as an Error not a warning:
ts.Diagnostic
Error
"'{0}' is declared but its value is never read.": { "category": "Error", "code": 6133, "reportsUnnecessary": true },
Suppose someone is writing new code and not quite finished yet.
const x: number = 123; const y: number = 321; const product: number = x*y; // TODO: Do something with "product"
They have not used x yet, but they certainly plan to use it when they are done writing their code. When you run tsc the output looks like this:
x
tsc
src/index.ts:9:5 - error TS6133: 'x' is declared but its value is never read.
With a professional build orchestrator, this "compiler error" will:
Proposal: Make it a warning instead:
"'{0}' is declared but its value is never read.": { "category": "Warning", "code": 6133, "reportsUnnecessary": true },
My suggestion meets these guidelines:
The text was updated successfully, but these errors were encountered:
This is entirely predicated on #13408, so should just be tracked there.
Sorry, something went wrong.
This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.
No branches or pull requests
Search Terms
TS6133 6133 noUnusedLocals
This is related but more general: #13408
Suggestion
This
ts.Diagnostic
message is classified as anError
not a warning:Examples
Suppose someone is writing new code and not quite finished yet.
They have not used
x
yet, but they certainly plan to use it when they are done writing their code. When you runtsc
the output looks like this:With a professional build orchestrator, this "compiler error" will:
Proposal: Make it a warning instead:
Checklist
My suggestion meets these guidelines:
The text was updated successfully, but these errors were encountered: