vscode-intelephense
vscode-intelephense copied to clipboard
Add @see and/or @link and its inline variants
Feature description or problem with existing feature
As far as I can see, intelephense doesn't seem to care about @see
or @link
and doesn't show any rendered links in the popover to methods, functions and the like.
Describe the solution you'd like Provide at least one way to link methods et. al. Preferably @see, @link and its inline variants {@see}, {@link}.
Additional context It would also be helpful, if there would be a link to a canonical standard for phpdocblocks intelephense uses.
Any update on this?
Still broken / Not implemented. Bug is 1 1/2 years old. If I use @see
I get undefined
in the documentation popup.
No any fix of that
Is there fix now?
Intelliphense is great otherwise, but yes I also see this issue and it's a shame because it would make doc comments so much better if cross-linking worked
I also have issues when @see {function}
cannot be resolved.
Also for variants of @see
description links, consider using @see {link} {description}
to resolve.
After reading the relevant specs, I think intelephense is only half done, not fully implemented @see.
according to @see - phpDocumentor
This is the one and only real issue i have with this otherwise wonderful extension...
Any update on this?
If implementing this feature directly in the popup text is not possible at all, a less cool but still useful alternative would be to add a destination to the list of possible "ctrl + click" destinations, for every @see
tag.
Any update on this?
bump
@see undefined
Premium user here, would love to see this fixed.
Also premium user. I think I have bought the extension at least twice, and i also encourage my coworkers to get it (or to ask their boss to get it). This would really be awesome. Been missing that feature for a while now.
I also became a premium user since this https://github.com/bmewburn/vscode-intelephense/issues/1316#issuecomment-1368567581 message haha.... some time has passed
If it were open source we could just try solve it ourselves and create a pull request... Shame.
Chiming in to say "we need this"