@suppress annotations

If you cannot easily fix a JsCompiler warning, you can suppress it using the @suppress annotation in the function's JSDoc block or the @fileoverview block.

Example

/**
 * ...
 * Good; suppresses within the entire function.
 * Also, this suppresses multiple warnings.
 * @suppress {visibility|underscore} 
 */
function blah() {
  /** @suppress {visibility} */ // Bad; doesn't work.
  otherClass.privateField_ = blah;

  /** @suppress {const} */  // Good; this is an exception (see below).
  SOME_CONSTANT = blah;
}

Other locations

Some specific @suppress annotations are allowed elsewhere:

• @suppress {const} and @suppress {duplicate} are valid on an assignment in statement position.
• @suppress {extraRequire} is valid just before a goog.require(...); statement.
• @suppress {missingRequire} is valid on any statement.

All other annotations can only be suppressed for a function or file. You cannot suppress most warnings for a single line within a function.

Suppression tags

The full list of suppressions accepted by the parser can be found in the jsdoc.suppressions list here.

The specific warnings included in each suppression can be found here (note that not all groups are recognized as suppressions)