If you cannot easily fix a JsCompiler warning, you can suppress it using the @suppress annotation.

The @suppress annotation is usable in a few places:

• a function's JSDoc block
• the @fileoverview block
• any variable declaration, assignment, or top-level expression such as a function call.

/**
 * ...
 * Good; suppresses within the entire function.
 * Also, this suppresses multiple warnings.
 * @suppress {visibility|underscore}
 */
function blah() {
  /** @suppress {visibility} */ // Good; suppresses within this declaration only.
  otherClass.privateField_ = blah;
  /** @suppress {checkTypes} */  // Good; suppresses the error in this line only
  foo(incompatible.type);
  /** @suppress {missingRequire} */  // Good; suppresses the missing require
  foo(blah.not.required);
  /** @suppress {checkTypes} */  // Bad; suppression not allowed here
  if (foo(incompatible.type)) {
    console.log("blah");
  }
}

Some specific @suppress annotations are allowed elsewhere:

• @suppress {extraRequire} is valid just before a goog.require(...); statement.
• @suppress {missingRequire} is valid on any statement.
• @suppress {with} is valid on with statements e.g. /** @suppress {with} */ with(Math) { alert(PI);} suppresses JSC_USE_OF_WITH warning.

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).

This table maps all suppressible error ids to the corresponding @suppress tag. Note that some errors are not suppressible in code and are omitted from this table.

These suppression tags are not canonical. In some cases multiple tags may suppress the same error.