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

[Feature Request]: Support "import hierarchy" in language server #26103

Open
jabraham17 opened this issue Oct 16, 2024 · 0 comments
Open

[Feature Request]: Support "import hierarchy" in language server #26103

jabraham17 opened this issue Oct 16, 2024 · 0 comments
Labels
area: Python bindings For things related to chapel-py, chpl-language-server, chplcheck, etc. area: Tools type: Feature Request

Comments

@jabraham17
Copy link
Member

jabraham17 commented Oct 16, 2024

Today, we already make use of the call hierarchy feature of LSP to show the chain of calls that are used for a given function. Modules can also have similar chains, via use/import. An interesting feature to explore is if we can show an "import hierarchy" using the same LSP feature.

This would for a given import show which modules that brings in, and then which modules those bring in, and so on. This could also be used to show all the places a given module is used.

This is likely a bigger effort, as we would need to plumb more dyno scoping features in chapel-py and need to figure out how to "hack" the call hierarchy to work with imports

@jabraham17 jabraham17 added type: Feature Request area: Tools area: Python bindings For things related to chapel-py, chpl-language-server, chplcheck, etc. labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Python bindings For things related to chapel-py, chpl-language-server, chplcheck, etc. area: Tools type: Feature Request
Projects
None yet
Development

No branches or pull requests

1 participant