31 ms·
I wish this issue would get addressed: https://github.com/microsoft/vscode/issues/94679 https://github.com/microsoft/vscode/issues/94679 Showing fully resolved
by Rapzid 4y ago
I wish this issue would get addressed: https://github.com/microsoft/vscode/issues/94679 https://github.com/microsoft/vscode/issues/94679
Showing fully resolved types in Intellisense would be the single largest usability enhancement they could make for me right now..
- uup 4y agoThe Id<T> type defined in the first comment seems like a pretty good, albeit ideally unnecessary, workaround.
- Rapzid 4y agoThose hacks work but in practice I wouldn't classify them as "good". You end up having to look at a ton of types including in library code like React and etc that can be quite complex. Having to stop and try to wrap those on the fly is terrible ergonomics.
- uup 4y agoYou might also be able to leverage typeof in conjunction with Id<T>. Like if you have some parameter x with a complex type you can create a temporary variable of type Id<typeof x> to avoid looking up any additional types. Totally agree it should be supported out of the box, however.
- lf-non 4y agoYeah, this is a recurring pain. I know the universe at large has moved away from eclipse, but I loved their rich tooltips where you had nice structured representation (not just a blob of text from lsp) and could click through and navigate the type hierarchy.
- 9dev 4y agoTry any IntelliJ IDE, they’ve got that. I can’t understand why anyone would want to use VS Code with a Typescript project voluntarily…