Enable the no-unused-vars
ESLint rule
Please see http://eslint.org/docs/rules/no-unused-vars; note that this patch purposely uses the same rule options as in `mozilla-central`, such that it fixes part of issue 7957. It wasn't, in my opinion, entirely straightforward to enable this rule compared to the already existing rules. In many cases a `var descriptiveName = ...` format was used (more or less) to document the code, and I choose to place the old variable name in a trailing comment to not lose that information. I welcome feedback on these changes, since it wasn't always entirely easy to know what changes made the most sense in every situation.
This commit is contained in:
parent
8d684b5b3f
commit
52e0f51917
23 changed files with 37 additions and 85 deletions
|
@ -36,7 +36,6 @@ var MessageHandler = sharedUtil.MessageHandler;
|
|||
var MissingPDFException = sharedUtil.MissingPDFException;
|
||||
var UnexpectedResponseException = sharedUtil.UnexpectedResponseException;
|
||||
var PasswordException = sharedUtil.PasswordException;
|
||||
var PasswordResponses = sharedUtil.PasswordResponses;
|
||||
var UnknownErrorException = sharedUtil.UnknownErrorException;
|
||||
var XRefParseException = sharedUtil.XRefParseException;
|
||||
var arrayByteLength = sharedUtil.arrayByteLength;
|
||||
|
@ -448,7 +447,7 @@ var WorkerMessageHandler = {
|
|||
var responseExists = 'response' in xhr;
|
||||
// check if the property is actually implemented
|
||||
try {
|
||||
var dummy = xhr.responseType;
|
||||
xhr.responseType; // eslint-disable-line no-unused-expressions
|
||||
} catch (e) {
|
||||
responseExists = false;
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue