Comment by kroltan | Hacker News Reader

Comment by kroltan | Hacker News Reader

Parent Full thread

I don't think "unresolved variable" is listed as an actual error in plain JS in WebStorm? At least by default.

In any case, like any inspection, you can adjust its severity to whatever you find appropriate, including "don't show it at all".

File > Settings > Editor > Inspections > Javascript and Typescript > General > Unresolved reference.

Or directly from the "Show Context Actions" action (Alt+enter or whatever you have it set to, the same combination that shows refactoring actions), you can navigate the inspection like a submenu and select "Edit inspection profile setting".

https://i.imgur.com/3XCwxI1.png

It is not an error true but it shows in the list with a yellow icon. But that means my list of "problems" is huge (because I prefer the shorter version of the expression). I would like the problems-list to be empty.

The problem is the long list often hides real errors in it. I would like to spot those more easily.

But I'll try your suggestions, maybe there's a way to make this warning disappear altogether from the list.

I still don't think, and don't understand, why it is a "problem" since the equivalent longer expression is not. It feels like WebStorm is mandating its own JavaScript-rules on me and my programming style.

UPDATE: I just double-checked and I see many errors like this:

    Unresolved variable someFieldName

which are preceded by a RED round icon containing a '!'.

It certainly looks like an error because it is red and there are also other problems listed which are preceded by a yellow-background icon.

So I think WebStorm thinks this is an error, not a warning.

Reply on news.ycombinator.com