-
Notifications
You must be signed in to change notification settings - Fork 413
Separate CliAction into synchronous and asynchronous types
#2205
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
jonsequitur
merged 19 commits into
dotnet:main
from
jonsequitur:CliAction-improvements-2
Jun 8, 2023
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
5e4548d
wip
jonsequitur bfaa2cf
wip
jonsequitur 319ac56
split CliAction into sync and async types
jonsequitur 7cc0dfa
minor cleanups
jonsequitur f660766
Move typo corrections into ParseErrorAction, make it public
jonsequitur 85df88f
rename test class
jonsequitur b826e78
bring back (internal) anonymous CliAction types
jonsequitur 986ef79
Change exception to be a debug-only check
jonsequitur 1e29583
update API baselines
jonsequitur 8334e65
generalize precedence of directive actions over option actions
jonsequitur f25af14
split into separate files, add XML doc comments
jonsequitur f06f115
rename DiagramAction to ParseDiagramAction
jonsequitur 69f4205
split CompletionAction into a separate file
jonsequitur 7e0b55a
update baseline
jonsequitur c65020e
exclude benchmarks project
jonsequitur 008524c
Address PR comments
jonsequitur 51af30f
support non-terminating option actions
jonsequitur 8fd95c4
reuse IsBoolean() method
jonsequitur 801bf54
update API baseline
jonsequitur File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| <SolutionConfiguration> | ||
| <Settings> | ||
| <AllowParallelTestExecution>True</AllowParallelTestExecution> | ||
| <CustomBuildProperties> | ||
| <Value>TargetFrameworks = net7.0</Value> | ||
| <Value>TargetFramework = net7.0</Value> | ||
| </CustomBuildProperties> | ||
| <SolutionConfigured>True</SolutionConfigured> | ||
| </Settings> | ||
| </SolutionConfiguration> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just thinking out loud here: should we keep all actions in the
System.CommandLine.Invocationnamespace?For example to me
ParseErrorActionbelongs inSystem.CommandLine.Parsingas it's related to parsing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My thought here was that since the entire invocation space is a effectively a different layer and could be replaced with a completely different invocation infrastructure on top of the same parser, none of these belong under parsing.