-
Notifications
You must be signed in to change notification settings - Fork 131
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
Go to (local) module implementation from source
#558
Comments
This functionality has been released in v0.27.0 of the language server. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Use-cases
See hashicorp/vscode-terraform#669
Notes
One would be tempted to use the "go to implementation" LSP method for this but according to how it is implemented in VS Code, this may not be the appropriate use.
It seems that this is meant to be used in contexts of "interface implementations" in languages that have interfaces, hence the plural.
Proposal
Go To Definition
Use native
textDocument/definition
method to associate module URIs with relevantsource
attribute values.This will be surfaced as Cmd/Ctrl+click-able and via context menu in most IDEs.
The text was updated successfully, but these errors were encountered: