How to make balloons go away
WebStorm is a little too helpful for me, and is constantly showing balloon tips on top of some functions. How can I turn off this "feature"?
Also, what the balloon says does not make sense to me. It says:
Initializer type Function is not assignable to variable type...
I have no idea what this is supposed to mean. It is as if WebStorm makes some pretty significant assumptions about the patterns being employed. In my case I'm just assigning a function to a variable. Nothing too fancy really. I would like to exercise some control over what patterns WebStorm expects. I have the same general problem with the code inspection feature where there are apparently implicit assumptions about the structure of the code which do not hold true for my code.
Are these assumptions documented somewhere? ---- I'm moving from JSLint which I was able to make happy, and now I have this new tool with new demands. How can I control WebStorm's expectations?
Thanks!
请先登录再写评论。
I got this particular balloon / tooltip to go away by using a separate var to declare each variable to which I was assigning a function, but JSLint is going to give me hell about not using a single var. I still don't know how to turn off these baloons in general; and still not sure why WebStorm thinks this is a problem in the first place. It's pretty frustraing when a tool designed to improve productivity pesters you to death with non-issues.
Do not bother, this is a bug, we will fix it.
Is there a workaround to this issue (other than using a separate 'var') ? ...and is there an ETA for a fix? While WebStorm is a great web development tool, it's FAR from useful with this kind of warnings all around the code.
Please post code snippet exhibiting the problem
Here is an example. The comments seem to be the cause of the warnings. WebStorm might not treat them properly. From ECMA-262 spec.
Attachment(s):
snippet.js
Thank you for the code snippet, WebStorm (unsuccessfully) uses comment information as type hint and tries to validate that. I will fix the issue right now.
Thank you! This little fix will improve WebStorm a lot as a Javascript IDE.
I just installed WebStorm 3.0.3 and was glad to see that it fixed the comment bug. Thank you!