-
Notifications
You must be signed in to change notification settings - Fork 488
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
Stopping formatting from resolving pathexec #2104
Comments
In fact this is fixed by PSScriptAnalyzer 1.18.1 already: PowerShell/PSScriptAnalyzer#1210 (comment). If you run We'll also be releasing an update of the extension in the next week or two that includes the updated PSScriptAnalyzer dependency. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
If I have a command that can be resolved to an .exe or .cmd or another PATHEXT extension, formatting the document adds the extension to it.
e.g.
node --version
becomes
I would like to be able to stop this from happening somehow.
Why would this be a problem if it's accurate you may ask? Because I'm trying to write a PowerShell script that would be ran via PowerShell core on Linux, where "node" is just "node", not "node.exe". That same script is also compatible with Windows and PowerShell 5.1, but to achieve the cross platform compatibility, the extensions are intentionally removed.
Environment Information
Visual Studio Code
PowerShell Information
Visual Studio Code Extensions
Visual Studio Code Extensions(Click to Expand)
The text was updated successfully, but these errors were encountered: