-
Notifications
You must be signed in to change notification settings - Fork 404
[1653] remove the legacy double dash behavior and ParseResult.UnparsedTokens #1806
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
[1653] remove the legacy double dash behavior and ParseResult.UnparsedTokens #1806
Conversation
@@ -243,7 +235,7 @@ private void ParseRemainingTokens() | |||
} | |||
else if (foundEndOfArguments) | |||
{ | |||
AddCurrentTokenToUnparsed(); | |||
AddCurrentTokenToUnmatched(); |
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.
I don't think this is the right behavior. This should probably not be doing anything special at this point. If you remove the call to AddCurrentTokenToUnmatched
do all of the tests pass?
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.
Yeah, you are right. The whole method become useless. I removed it.
Thanks, @Tunduk! |
@jonsequitur Thanks for you review! |
Yes we can! |
This PR fixes an issue #1653