Skip to content
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

Some updates to the docs, including subsystem flow #2487

Draft
wants to merge 1 commit into
base: main-powderhouse
Choose a base branch
from

Conversation

KathleenDollard
Copy link
Contributor

No description provided.

* The CLI author decides that they want all available functionality. They can use the pipeline without invocation if they would prefer to map values to parameters and invoke themselves.
* The CLI author winds up with several subcommands and determining which code to call and mapping becomes a bit messy or a burden. At this point, they can add invocation.

Of course folks may jump into this flow anywhere, and all four scenarios will be supported. The need for this flexibilty is one of the things we learned from feedback on existing main (the current preview of System.CommandLine that we are replacing).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

flexibility

@KathleenDollard KathleenDollard added the Powderhouse Work to isolate parser and features label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Powderhouse Work to isolate parser and features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants