-
Notifications
You must be signed in to change notification settings - Fork 369
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
Design proposal for interactive invocation #6015
Conversation
…uple open questions
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.
Love it!
I like it! |
|
||
## Workflow | ||
|
||
When a user invokes a template, the command should evaluate the user-provided parameters and determine if it should enter interactive mode. This is done by checking if the command is being invoked from a terminal (i.e. isatty is true) and if the command has any symbols that are of type `parameter` and are required _while also having required symbols that are not explicitly provided_. If both of these conditions are true, the command should enter interactive mode. |
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.
This sounds very reasonable. Below in Detecting interactive mode
, there is only the explicit opt-in option.
Do we want implicit switch to interactive mode under the conditions outlined here as well? Or not for the initial version?
This PR adds a proposed design doc for interactive invocation to open it up for discussion. I've focused on the invocation scenario for now - there are enough open questions to discuss that will likely take a bit to work through.
Need more details on