You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduced in 1.7.2, when using TAP to parse arguments, arguments with quotes within the argument remove the quote. This was likely introduced when handling quoted arguments. It appears to be the same for either quote style.
For instance: --foo b'a'r
is parsed as: foo: 'bar'
It works fine if the argument is quoted though, so perhaps this is not an issue: --foo "b'a'r"
is parsed as: foo: 'b\'a\'r'
The text was updated successfully, but these errors were encountered:
Great point! We agree this is an issue. We should check if a string is enclosed in quotation marks before remove quotation marks. As you might have guessed from the lag in the reply, it might take a while. PRs appreciated... we'll try to get to it soon!
The only solution is unfortunately to use "b'a'r" or b\'a\'r. And it's the same for any other command from any other tool, because the parsing is done at the shell level.
Introduced in 1.7.2, when using TAP to parse arguments, arguments with quotes within the argument remove the quote. This was likely introduced when handling quoted arguments. It appears to be the same for either quote style.
For instance:
--foo b'a'r
is parsed as:
foo: 'bar'
It works fine if the argument is quoted though, so perhaps this is not an issue:
--foo "b'a'r"
is parsed as:
foo: 'b\'a\'r'
The text was updated successfully, but these errors were encountered: