-
Notifications
You must be signed in to change notification settings - Fork 290
Dash dash support in FormatCommandLine (unparser) #254
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
Comments
scadorel
added a commit
to scadorel/commandline
that referenced
this issue
Oct 12, 2015
Good call. We don't escape arguments even though we should. However, I would like to point out that option1 will have a double dash in your expected output: |
You're right, thanks. Missed a dash in the sample 👍 |
gsscoder
added a commit
that referenced
this issue
Oct 16, 2015
PR has been merged and validated. Closing issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
When using value options with dash inside some of them, the generated command line generated by the FormatCommandLine method is not correct.
The sample with generate --option1 test powershell -version 3.0 D:\test.ps1 but "-version" switch will be detected by the library as an invalid option and will raise an error.
It might be good to use the dash dash syntax with the unparser to avoid the issue.
Expected result: --option1 test -- powershell -version 3.0 D:\test.ps1
What do you think ?
I will send a PR shortly.
The text was updated successfully, but these errors were encountered: