PowerShell / PowerShell/vscode-powershell
Semantic Highlighting: Namespace types incorrectly highlighted as functions
Open
Nobody has claimed this yet.
Area-Semantic Highlighting
Issue-Bug
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
- I have read the troubleshooting guide.
- I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
- I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
- If this is a security issue, I have read the security issue reporting guidance.
Summary
This should be highlighted as a type, not a function.
Example of correct highlighting:
PowerShell Version
N/A
Visual Studio Code Version
1.68.0-insider
ba2dd825803b5f95d5dcce927afc3a4882ed0f84
x64
Extension Version
ms-vscode.powershell-preview@2022.5.5
Steps to Reproduce
Add the text.
Visuals
No response
Logs
No response
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
Start by reproducing the namespace example in Visual Studio Code using the screenshots and the stated extension and VS Code versions. Compare the semantic highlighting classification with the correct example; done means namespace types are highlighted as types rather than functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100