HoriSun / closure-compiler

Automatically exported from code.google.com/p/closure-compiler
0 stars 0 forks source link

"Bad type annotation. Unknown type" expressions are not suppressible #1281

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Have code with a bad type expression:

/** @this {SomeFoo} */
function f() {}

Using @suppress {typeCheck} at either the file or function level does not 
suppress the warning.  The root cause is that the suppression warning guard 
only operates on JSError objects with an associated node, but Rhino warnings 
(parser, type parsing, etc) do not have associated nodes.

It would be nice if these could be handled more consistently.  Hopefully the 
new parser and type system with remove the disconnect between the rhino and 
compiler error reporters.

Original issue reported on code.google.com by concavel...@gmail.com on 12 Mar 2014 at 8:15

GoogleCodeExporter commented 9 years ago
Issue tracking has been migrated to github. Please make any further comments on 
this issue through https://github.com/google/closure-compiler/issues

Original comment by blic...@google.com on 1 May 2014 at 6:31

GoogleCodeExporter commented 9 years ago

Original comment by blic...@google.com on 1 May 2014 at 6:34