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

"whilespace" in PSScriptAnalyzer(PSMisleadingBacktick) #233899

Closed
FrankCarius opened this issue Nov 15, 2024 · 4 comments
Closed

"whilespace" in PSScriptAnalyzer(PSMisleadingBacktick) #233899

FrankCarius opened this issue Nov 15, 2024 · 4 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@FrankCarius
Copy link

Type: Bug

Short cosmetic issue "whilespace" instead of "whitespace"

  1. Start VSCode with a new PowerShell File. (ps1)
  2. Add the following code (there is a space after the backtick)

get-item `
-path c:\temp

  1. Wait for the Hint about "PSMisleadingBacktick" from PSScriptAnalyzer
  2. click on "quick fix"
    The Menue offers "Remove training whilespace" "l" instead of "t"

VS Code version: Code 1.95.2 (e865366, 2024-11-07T11:07:22.054Z)
OS version: Windows_NT x64 10.0.26100
Modes:

Copy link

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.95.3. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

@FrankCarius
Copy link
Author

Just updated and the typo is still there

Version: 1.95.3 (user setup)
Commit: f1a4fb1
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100

@mjbvz
Copy link
Collaborator

mjbvz commented Nov 15, 2024

/extPowershell

Copy link

It looks like this is caused by the PowerShell extension. Please file the issue to the PowerShell extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.

Happy Coding!

@vs-code-engineering vs-code-engineering bot added the *caused-by-extension Issue identified to be caused by an extension label Nov 15, 2024
@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

2 participants