Skip to content
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

feat: go to definition on modules #95

Closed
astorath opened this issue Mar 1, 2019 · 4 comments
Closed

feat: go to definition on modules #95

astorath opened this issue Mar 1, 2019 · 4 comments
Labels

Comments

@astorath
Copy link

astorath commented Mar 1, 2019

It would be very helpful to have an options to:

  1. go to variable definitions from module statement params to module source,
  2. go to module dir from module source statement.
@paultyng paultyng transferred this issue from hashicorp/vscode-terraform May 12, 2020
@radeksimko
Copy link
Member

I may create a parent issue for the overall support of "go to definition" and list all the contexts where this may be useful, but yes - module and the contexts you outlined is where "go to definition" certainly makes sense. 👍

@radeksimko

This comment has been minimized.

@radeksimko
Copy link
Member

I have created individual issues to track mentioned functionality here with some more details:

  1. Go to variable definition (from local module arg) vscode-terraform#670
  2. Go to (local) module implementation from source vscode-terraform#669

Tracking these separately will help us plan the work on our roadmap as smaller chunks.

With that in mind I'm going to close this issue.

Thanks for the ideas!

@github-actions
Copy link

github-actions bot commented Sep 5, 2021

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants