Proposed rule change: no-unused-vars should consider a var "used" in JSDoc

• ESLint Version: 4.3.0
• Node Version: 7.10.1
• npm Version: 4.2.0

---

What rule do you want to change?

• no-unused-vars

Does this change cause the rule to produce more or fewer warnings?

• Fewer warnings

How will the change be implemented? (New option, new default behavior, etc.)?

• New default behavior

Please provide some example code that this change will affect:

import Foo from "foo";
/**
* @param {Foo} f
*/
function bar(f){ return f.baz; }

What does the rule currently do for this code?

• The rule flags the first instance of Foo (in import Foo) as an unused var.

What will the rule do after it’s changed?

• The rule should not flag Foo as unused because it is referenced in the JSDoc.

[clshortfuse]

VSCode (and Typescript) now supports

/** @typedef {import('../foo/bar').baz} baz */

So you don’t have to perform unused imports anymore.

[ChadKillingsworth]

As a maintainer of closure-compiler, I can pipe in here. The scope of a JSDoc comment is exactly where it occurs. From the above example:

import Foo from 'foo';

{
  const Foo = somethingElse;
  /**
   * @param {Foo} what does this mean? -- it means somethingElse. No ambiguity at all.
   */
  function x() {}
}