Is there a "supress all checking" annotation?

Like many people, I'm trying to use the inspectors built into webstorm, but like everyone I get a ton of spurious warnings.

Obviously some can be disabled in the GUI, and some can be overridded with comments, and come can be coded around.

But is seems there are some that just can't be overridden. And there is no way to code around them. An infamous one is that express uses "static" as a function name, but JSLint insists that this is illegal.

It would be amazing if there were an annotation that said "don't check anything at all on the next line". Is there such a thing?

Baring that, is there a guide to the annoations that let one turn off individual warnings?

6 comments
Comment actions Permalink

Please try

//noinspection all
0
Comment actions Permalink

It doesn't work.

Here is my code example:

// noinspection all
app.use("/", express.static(p));



I get a red underline under the 's' in 'static', with the text: "JSHint: expected identifier, but saw 'static' (a reserved word)".
0
Comment actions Permalink

It's great that noinspection all will work in future. Reading the linked issue it isn't obvious to me how these issues are related (I read it twice, and I still don't see it).

But I'll take your word for it that it will be fixed in 6.0

thanks!

0
Comment actions Permalink

The linked issue is about adding support for "//noinspection JSLint" and "//noinspection JSHint".
Seems you have similar problem: JSLint warns about using "static" function name.

0
Comment actions Permalink

Yes, they are related that way.

But - I think no matter how much you try there will alwasy be spurious warnings from various checkers, so it's absolutely essential that any warning can be surpressed by the user.

0

Please sign in to leave a comment.