You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 relevant source 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:
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
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: