vscode-powershell: CodeLens References not working if function is in another file
System Details
System Details Output
### VSCode version: 1.41.1 26076a4de974ead31f97692a0d32f90d735645c0 x64
### VSCode extensions:
alefragnani.Bookmarks@10.6.0
eamodio.gitlens@10.2.0
Ionide.Ionide-FAKE@1.2.3
Ionide.Ionide-fsharp@4.4.4
Ionide.Ionide-Paket@1.12.0
ms-vscode.csharp@1.21.9
ms-vscode.powershell@2020.1.0
ms-vscode.powershell-preview@2020.1.0
streetsidesoftware.code-spell-checker@1.7.20
### PSES version: 2.0.0.0
### PowerShell version:
Name Value
---- -----
PSVersion 7.0.0-rc.1
PSEdition Core
GitCommitId 7.0.0-rc.1
OS Microsoft Windows 10.0.18363
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Issue Description
CodeLens References does not work if the function is in another file. Both files shown below are in the same folder.
Note the 1 reference above the Y function definition. This is in the same file as the reference.
Note the 0 reference above the X function definition. This is in a different file to the referenc.
I wonder if this is related to: CodeLens References link only jumps to definition #2374.
Expected Behaviour
In TestModule.psm1 I expected to see 1 references above the X function definition.
Actual Behaviour
In TestModule.psm1 I see 0 references above the X function definition
Also Find All References for function X shows:
Find All References for function Y shows:
Attached Logs
PowerShell Extension Logs.txt PowerShell Editor Services Log.txt
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 27 (18 by maintainers)
You don’t have to tell me that 😃 While I code only in PowerShell over my modules I get how hard some things are and that resources are slim. I have 40 PS modules that I manage mostly alone with some help from the community. I appreciate all the work you and your team do. I’ll keep opening bugs/feature requests to make sure everything runs great. Even my F5 debug issue is no big deal now after you taught me how to “workaround” it - since I see what is happening now.
So take your time 😃 I just wish there was a much faster process for preview between fix and release date so those small bugs like this one would go away faster than once per month. But as you explained, it’s not an automated process so until that is done I’m fine 😃 I automated my PowerShell modules building just so I don’t have to spend time doing manual releases because I release modules daily, even multiple times per day.
@TylerLeonhardt With regard to
Go to Definitionand workspaces, I’ve tried the latest stable and test versions of the extension. Both give the following message:No definition found for '<function name>'.Looking at the comments on the issue created by @PrzemyslawKlys, it looks like this functionality has not yet been added.
I hear ya. There are a ton of opportunities for rich feature experiences for PowerShell in VS Code.
Unfortunately/fortunately, we had to focus on stability and performance for the past 2 years, peppering in small features as we go.
Plus there’s really only 1 dev working on this at any given time so the resources are slim.
We’re trying though. I hope that’s visible.
@TylerLeonhardt As requested:
[2020.1.0 Preview] Find All References shows two entries for the function definition #2433
Well I’ve opened this issue a while ago: https://github.com/PowerShell/vscode-powershell/issues/2112
It wasn’t supported for multiple workspaces in the "old version’. But that would be cool if it would be possible. During development, I am often separating some code into different modules and it makes it much harder to debug things if only 1 workspace shows references.
@TylerLeonhardt I’ve installed the new VSIX and done a quick test. Both
referencesandGo to Definitionare working.