You can also right-click to adjust the font size for better readability. To try this feature out, click the icon in the gutter, next to the comments, and you’ll see documentation comments displayed without any distractions. More details in the demo project.ĭoes anyone know why this might be happening? Is it a bug in WebStorm, or something where WebStorm and VS Code disagree on the correct course of action? Or perhaps I should be hinting the types in. To make it a bit easier, you can try rendering those comments in the editor. The demo also contains three examples where I was able to get WebStorm to resolve the types properly, but each approach came with its own issues. Auto-completion provides suggestions from global "Client" type (in this case, from .ts): Entirely unknown type, or guessed as "Object":Ģ. Since the module's types rely on those are installed as well.īelow are screenshots of the two examples in the demo (from index.js, project linked above) where types don't work properly for auto-completion (see full demo project for more context). The module supplies its own typings and they work correctly in e.g. In the demo linked above, WebStorm is unable to resolve types (hinted with JSDoc) from the "discord.js" module for auto-completion in certain situations when using require() in a. Tested with project inside WSL2 and outside. Using WebStorm 2020.2 with Node.js 14.7.0 (but also confirmed issue appears when using Node.js 12) on Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |