-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Fix: Fixed an issue with the 'Run with PowerShell' action not supporting files with spaces in their names #16455
Conversation
Co-authored-by: 0x5bfa <62196528+0x5bfa@users.noreply.github.com>
Please provide steps you validated this change. |
Hang on |
It looks like the issue is still present |
Yeah I know I'm working on it |
Yes I'm aware, I'll try again with it a bit later |
Sorry for opening the pr early before finding out whether the issue is fixed it's just the only way I can get the package is from the ci run. |
That's fine, I'll wait until it's ready. |
There's still something else I haven't tried but it's unlikely to work. |
This should fix the issue return Win32Helper.RunPowershellCommandAsync($"\"{context.ShellPage?.SlimContentPage?.SelectedItem?.ItemPath}\"", PowerShellExecutionOptions.None); |
That didn't work for me, see |
I forgot to add a space to the file name when I tested 😀 |
This should work (I tested a file with a space this time). return Win32Helper.RunPowershellCommandAsync($"& '{context.ShellPage?.SlimContentPage?.SelectedItem?.ItemPath}'", PowerShellExecutionOptions.None); |
Co-authored-by: Yair <39923744+yaira2@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Resolved / Related Issues
To prevent extra work, all changes to the Files codebase must link to an approved issue marked as
Ready to build
. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.