[kroltan]

Not really at all, the type checker understands it is a field reference (it's just an alternative syntax after all, it is absolutely 0% difference in behaviour.

However, it's a common typed-javascript idiom to use string-indexing when you're probing a value of unknown type. Even Typescript has settings to accept this.

[galaxyLogic]

I get it it's a nice idiom. But neither version is an error and the "correct" version is more verbose. Less verbose is better in my preference when it is just as clear or even clearer (because it is less verbose). And this is not TypeScript but JavaScript.

I guess my question is, how can I make the

    ob.something 

NOT be (listed as) an error? When is it not an error (according to WebStorm linter)?

[kroltan]

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

[galaxyLogic]

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.

[galaxyLogic]

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.