Skip to content

[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

Merged

Conversation

Tunduk
Copy link
Contributor

@Tunduk Tunduk commented Jul 26, 2022

This PR fixes an issue #1653

@@ -243,7 +235,7 @@ private void ParseRemainingTokens()
}
else if (foundEndOfArguments)
{
AddCurrentTokenToUnparsed();
AddCurrentTokenToUnmatched();
Copy link
Contributor

@jonsequitur jonsequitur Aug 1, 2022

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?

Copy link
Contributor Author

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.

@jonsequitur jonsequitur merged commit 4b60585 into dotnet:main Aug 2, 2022
@jonsequitur
Copy link
Contributor

Thanks, @Tunduk!

@Tunduk
Copy link
Contributor Author

Tunduk commented Aug 2, 2022

@jonsequitur Thanks for you review!
Can we close the issue too?

@Tunduk Tunduk deleted the 1653-remove-legacy-double-dash-behavior branch August 2, 2022 16:12
@jonsequitur
Copy link
Contributor

Yes we can!

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

Successfully merging this pull request may close these issues.

2 participants