Skip to content

Fixes #2117 #2125

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

Conversation

phil-allen-msft
Copy link
Contributor

Fixes #2117

The main command "tofile", if it has arguments that are enclosed in double quotes, will receive them as independent elements in the args array. When the call to dotnet exec is made to invoke the subcommand "_tofile", if there are any arguments that contain spaces, they will now be regarded as multiple arguments and the subcommand run will have a different set of arguments, ones that do not match the users' intentions.

Uses the existing EscapePath to enclose those parameters that contain spaces with double quotes. The result is that if the paths that are arguments for the "tofile" command (startupassembly or --output) contain spaces, they should now be seen by the subcommand the same as they were in the main command.

@domaindrivendev domaindrivendev merged commit 2fc1ac3 into domaindrivendev:master May 22, 2021
@domaindrivendev
Copy link
Owner

Excellent thank you 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dotnet swagger tofile fails if any parameters contain spaces (even if quoted)
2 participants