Icons are completely messed up in Visual Studio member list about typescript HOT 4 OPEN

One more case:

Icon of Properties is displayed for Functions (among completions):

While the correct icon is displayed in quick info:

from typescript.

Hello @Peter-Juhasz! Given that this issue is specific to Visual Studio's completion, could you please move this discussion to a new issue in https://developercommunity.visualstudio.com/VisualStudio? Thank you!

from typescript.

Hi @MariaSolOs,

I reported the issue here for the following reasons:

• Since Visual Studio provides only the hosting and presentation, it is controlled by the language service what to display. In this case, it is the responsibility of the TypeScript language service to choose the correct icons what Visual Studio should display. The same way, if there is an issue only with TypeScript in VSCode, the issue won't belong to the VS Code repo I guess, but here. And on the videos I've provided you can clearly see that it works very differently in different settings. So, my assumption was that the issue is with the TypeScript language service, it selects the icons incorrectly for the completions items to display in same cases (while it works correctly for the quick info), and not with Visual Studio.
• The language service is implemented in this repo, and I have found many similar issues related to completion and tracked here.
• I had a very bad experience with the VS reporting earlier, even when detailed reproduction, recordings are provided, they are closing them blindly usually with "not enough info" and that's it.

If you are confident that the issue is with Visual Studio, could you route it to the appropriate team, please? You can provide much more insider details than me, even if it slips only on the integration of the language service and VS. Thank you.

from typescript.

Hi Peter!

Both Maria and I work in the team that provides TypeScript and JavaScript experiences in VS. I'm sorry we haven't provided the level of answers you expected before, we try our best.

We know where the issue is here, and we would prefer to be tracking in the right systems. If you can create an issue in developer community for this and copy the link here, I'll make sure it gets immediately routed to us. Just copying and pasting this should be fine, you did an awesome job in explaining what the issue is.

Thanks!
J

from typescript.