Feature request: "Go to Definition" works across all files in a workspace

[adbertram]

It'd be super-convenient for me if I could right-click on a function call click "Go to Definition" and it would find the module (if exists) that's in my current workspace, open up that file and then go to the function declaration.

[daviwil]

Yep, we have a lot of work to do on the symbol features in PowerShell Editor Services. We need to start working on module-level analysis to enable this.

[TylerLeonhardt]

This sounds close to #420. There should be some overlap but I'm not certain if/what unique changes there are to these two issues.

[rfoust]

Hi, any updates on this? I stumbled across this issue when figuring out if CodeLens was supposed to look for function names across multiple modules in the workspace. I think this is related?

[TylerLeonhardt]

There's been some work to improve this. Probably not in the space you're hoping. I don't think I quite understand your comment - can you give an example, @rfoust?

[rfoust]

@TylerLeonhardt oops it's been a year, guess I'll reply now lol. :) I mean if I have multiple module folders open in the workspace and I'm looking at a function definition "function Get-Something" then right above it, it says "0 references" but there are really all kinds of references to it in other modules that I'm editing in my workspace, it just isn't seeing them.

[fflaten]

What's the scope of this issue?
Initial post reads like definitions in same workspace. That should work in general now. Multi-root workspaces (introduced later I believe) will still need some work.

Be aware that the lookup is not module-aware, so conflicting function names might cause multiple returned definitions and wrong reference count.

Tracking definitions across Import-Module (and PSIC-imported modules outside workspace?) sounds like a separate issue.

[andyleejordan]

@fflaten actually I just made multi-root workspaces work in the last preview! I believe this is finished, besides what you point out with imported modules. So let's close this and leave #420 open I think.

[ghost]

This issue has been marked as fixed. It has been automatically closed for housekeeping purposes.