-
Notifications
You must be signed in to change notification settings - Fork 185
Go to Definition in PHPDoc comments #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I would love to support this, but I don't get any location info from phpDocumentor for the tags. |
From @razvanphp on November 4, 2016 19:3 Maybe you can open a feature request issue there? |
PHP support for https://github.com/joelday/vscode-docthis has been a pretty big request. I'm working on switching to a multiple language architecture, but I want to make sure that I'm going in the right direction or if I should do this at all. I sent @mousetraps a quick e-mail about this, too. This is also pretty sensitive given the runtime implications of PHPDoc comments, which is going to require very careful testing and CI on my part. Any thoughts? |
@joelday I think this functionality can be provided much easier in the language server. But automatic documentation !== go to definition in docblocks. |
Totally. :) |
is this now possible due to adoption of Microsoft/tolerant-php-parser? |
@felixfbecker |
From @razvanphp on November 4, 2016 18:54
Not sure how I can explain better, but this would be very useful, especially for private variables in classes.
Thank you for this great extension, makes VSCode perfect!
Copied from original issue: felixfbecker/vscode-php-intellisense#28
The text was updated successfully, but these errors were encountered: