Skip to content

Remove non generic GetValue overloads #2059

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
merged 3 commits into from
Feb 18, 2023

Conversation

adamsitnik
Copy link
Member

@adamsitnik adamsitnik commented Feb 17, 2023

fixes #2058

One of the test was referring to #1647. With #2052 the users will be able to do:

object? value = parseResult.GetValue<object>(nonGenericOptionOrArgument.Name);

@jonsequitur I don't have a strong opinion whether we should wait with merging this PR until #2052 gets solved and the tests can be just updated instead of being removed.

# Conflicts:
#	src/System.CommandLine.ApiCompatibility.Tests/ApiCompatibilityApprovalTests.System_CommandLine_api_is_not_changed.approved.txt
#	src/System.CommandLine/Invocation/InvocationContext.cs
@adamsitnik adamsitnik merged commit 6462288 into dotnet:main Feb 18, 2023
@adamsitnik adamsitnik deleted the removeNonGeneric branch February 18, 2023 20:25
@KalleOlaviNiemitalo
Copy link

fixes #2056

No, this PR doesn't add a Directive type.

@KalleOlaviNiemitalo
Copy link

Instead fixes #2058.

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

Successfully merging this pull request may close these issues.

Remove non-generic GetValue methods
4 participants