nushell / nushell/vscode-nushell-lang
Go to definition for use statements
Nobody has claimed this yet.
- Dominant language
- Nushell
- Stars
- 153
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
I see that "Go to definition" works for used commands, but not for the the use statement.
For example:
use ../hello.nu hello
def main [] {
hello
}
Go to definition works on the hello call in the main function but not on the use statement on the first line.
Am I missing something in a configuration/setting or is this the current intended behavior?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the example in VS Code and compare go-to-definition on the hello command with the hello name in the use statement. Trace the extension's definition-navigation handling for use statements; done means the imported target is navigable from the use name as well as from the command call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100