You can always change the type mismatch highlighting style in Settings | Inspections | JavaScript | General | Type mismatch problem to get it more emphasized or disable it at all. Note that completion processor uses nearly the same info as type checking, so if type is specified in JSDoc annotation, properties of that type will be shown in completion list.

You can specify callback’s ‘this’ and parameter types, and they will be known in passed anonymous function. To make JSDoc comments more readable, we’ve improved the way WebStorm highlights JSDoc syntax. Type checking may even be helpful without explicit types annotations.Īnd this is my favorite case. WebStorm will now take file names into consideration when showing you completion suggestions for top-level variables as well as for function and class names. Return type is checked inside function and when its call result is used somewhere. To start with let’s consider the most basic situation:Įvery constructor function “becomes” a type and its name can be referenced inside JSDoc tags.Īrray of elements of some type could also be specified with (for example, Point).

For 5.0 release we’ve supported Google Closure types syntax, so that quite complex situations can be handled more accurately and conveniently.

I’m talking about static type checking when type of parameter or variable on the left side of assignment or function return type is explicitly specified in JSDoc annotation.

Today’s post is about a nice feature set (many of you have been using for a long time) and its recent improvements.

Jetbrains webstorm jsdoc