Currently, the only way to set inputs to CLI commands is to provide them as command-line arguments, which can be awkward (e.g. with the [dev] plt add-depl subcommand and its optional flags for setting feature flags). It would be nice if any CLI subcommand with required arguments could be invoked without any arguments, to trigger a simple TUI (e.g. https://github.com/charmbracelet/huh) for getting the arguments in a more user-friendly way. This could also be used to:
provide an editor interface (e.g. for a TUI-only [dev] plt edit-depl subcommand)
provide prompts for confirmation, as an alternative to erroring out without --force flag (e.g. as wishlisted in #229, which was closed without addition of TUI functionality)
We should add an optional global flag (e.g. --noninteractive/--nonint, or --frontend=nonint) to error out instead of going to a TUI when CLI args are underspecified.
Currently, the only way to set inputs to CLI commands is to provide them as command-line arguments, which can be awkward (e.g. with the
[dev] plt add-deplsubcommand and its optional flags for setting feature flags). It would be nice if any CLI subcommand with required arguments could be invoked without any arguments, to trigger a simple TUI (e.g. https://github.com/charmbracelet/huh) for getting the arguments in a more user-friendly way. This could also be used to:[dev] plt edit-deplsubcommand)--forceflag (e.g. as wishlisted in #229, which was closed without addition of TUI functionality)We should add an optional global flag (e.g.
--noninteractive/--nonint, or--frontend=nonint) to error out instead of going to a TUI when CLI args are underspecified.