Skip to content

Remove non generic GetValue overloads#2059

Merged
adamsitnik merged 3 commits intodotnet:mainfrom
adamsitnik:removeNonGeneric
Feb 18, 2023
Merged

Remove non generic GetValue overloads#2059
adamsitnik merged 3 commits intodotnet:mainfrom
adamsitnik:removeNonGeneric

Conversation

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

fixes #2056

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

@KalleOlaviNiemitalo
Copy link
Copy Markdown

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