Why is this extension using the Visual Studio version of Doxygen doc hints?

[BlueStaggo]

We could be more ahead if this extension used a different method. This extension doesn't even support things like the @link tag!




These are just a few examples of many from GLFW that are broken. I heared that this extension replicates Visual Studio's method of generating these doc hints:

sean-mcmanus on #6650:
Related to #6399 . Behavior matches what VS shows.

michelleangela Do you know how to deal with this?

sean-mcmanus on #6084:
devabhishekpal That is implemented in our shared code with VS, not in our our open source TypeScript.

michelleangela on #6084:
This is not fixed yet. The code for this is common between the C++ extension and C++ language service on Visual Studio. So once the issue (tracked by feedback ticket) is addressed for Visual Studio, the C++ extension will be able to port over the fix.

So what's this talk about using Visual Studio's language service? If Visual Studio's Doxygen doc hints are so bad, why don't we make our own? Is it too complicated or difficult or is it impossible to do such a thing? Also, apologies if I am getting the name wrong.

[sean-mcmanus]

Yeah, our implementation backed for VS Code doc comments is shared with VS. We have some existing issues tracking supporting more doxygen tags and stuff.

[BlueStaggo]

A problem is that I can't find an extension that implements their own method for doc hints instead of using Visual Studio. Is that possible? The closest I can find is "Doxygen Previewer", but that doesn't work sometimes and it doesn't affect doc hints.

[sean-mcmanus]

I'm not aware of an alternative doc hint provider for VS Code.