Skip to content

Fix #2743 - allow Argument<T>.CustomParser to be set to null#2784

Merged
jonsequitur merged 3 commits intodotnet:mainfrom
jonsequitur:fix-2743
Apr 9, 2026
Merged

Fix #2743 - allow Argument<T>.CustomParser to be set to null#2784
jonsequitur merged 3 commits intodotnet:mainfrom
jonsequitur:fix-2743

Conversation

@jonsequitur
Copy link
Copy Markdown
Contributor

@jonsequitur jonsequitur commented Mar 17, 2026

Fixes #2743

The PR also includes timeout handling changes in the tests where CI was tripping up often enough to bundle that fix into this PR to ensure it could be green.

@KalleOlaviNiemitalo
Copy link
Copy Markdown

Contains changes from #2783, too.

@jonsequitur jonsequitur force-pushed the fix-2743 branch 2 times, most recently from b658ec0 to 5411438 Compare March 18, 2026 15:24
@jonsequitur jonsequitur reopened this Mar 18, 2026
@jonsequitur jonsequitur changed the title Fix #2743 Fix #2743 - allow Argument<T>.CustomParser to be set to null Mar 31, 2026
Comment thread src/System.CommandLine/Invocation/InvocationPipeline.cs
@jonsequitur jonsequitur merged commit baaad19 into dotnet:main Apr 9, 2026
9 checks passed
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.

CustomParser of Argument<T> cannot be reset by setting to null

3 participants