Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upUnused variables don't output warnings #1228
Comments
This comment has been minimized.
This comment has been minimized.
justinkalland
commented
Dec 20, 2018
|
From the best I can tell StandardJS has always skipped checking for unused arguments. I have created a pull request that changes the behavior. |
This comment has been minimized.
This comment has been minimized.
stale
bot
commented
Mar 20, 2019
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
label
Mar 20, 2019
stale
bot
closed this
Mar 27, 2019
lock
bot
locked as resolved and limited conversation to collaborators
Jun 26, 2019
feross
reopened this
Jul 11, 2019
stale
bot
removed
the
stale
label
Jul 11, 2019
standard
unlocked this conversation
Jul 11, 2019
This comment has been minimized.
This comment has been minimized.
|
Discussion moving here: standard/eslint-config-standard#136 |
feross
closed this
Jul 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
jmz7v commentedNov 12, 2018
Problem:
The following small React component
link.jshas a useless destructured variable, it is not being caught by Standard.What version of standard?
Standard:
12.0.1What operating system, Node.js, and npm version?
OS:
macOS 10.14 (18A391)Node:
v10.11.0NPM:
6.4.1What did you expect to happen?
To get an error like
What actually happened?
From what I can recall this would previously output an error since this is a conflict with one of the rules of Standard
No unused variables.Output: