Skip to content

[1653] remove the legacy double dash behavior and ParseResult.UnparsedTokens - #1806

Merged
jonsequitur merged 2 commits into
dotnet:mainfrom
Tunduk:1653-remove-legacy-double-dash-behavior
Aug 2, 2022
Merged

[1653] remove the legacy double dash behavior and ParseResult.UnparsedTokens#1806
jonsequitur merged 2 commits into
dotnet:mainfrom
Tunduk:1653-remove-legacy-double-dash-behavior

Conversation

@Tunduk

@Tunduk Tunduk commented Jul 26, 2022

Copy link
Copy Markdown
Contributor

This PR fixes an issue #1653

else if (foundEndOfArguments)
{
AddCurrentTokenToUnparsed();
AddCurrentTokenToUnmatched();

@jonsequitur jonsequitur Aug 1, 2022

Copy link
Copy Markdown
Contributor

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
Copy Markdown
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
Copy Markdown
Contributor

Thanks, @Tunduk!

@Tunduk

Tunduk commented Aug 2, 2022

Copy link
Copy Markdown
Contributor Author

@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
Copy Markdown
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