Skip to content

Add ConsoleIo::isInteractive() and --no-interaction option - #19821

Open
dereuromark wants to merge 1 commit into
5.nextfrom
console-no-interaction
Open

dereuromark wants to merge 1 commit into
5.nextfrom
console-no-interaction

Conversation

@dereuromark

Copy link
Copy Markdown
Member

--quiet does two things: it lowers the output level and turns prompts off (setInteractive(false), so ask()/askChoice() return their defaults). You can't get one without the other. There is also no getter for the interactive state, so commands that want to skip a confirmation check the output level instead. cakephp/migrations SeedCommand does $io->level() > ConsoleIo::QUIET.

This adds:

  • ConsoleIo::isInteractive(): bool
  • --no-interaction, a default option that disables prompts but leaves output at the normal level. It is long-only because -n is already taken by plugins (bake fixture -n, cakephp-setup db_backup create -n). A command that defines its own no-interaction option still overrides it, since addOption() replaces same-named options.

--quiet keeps its current behavior. The interactive flag is now set before initialize(), not after it, so a prompt in initialize() respects --quiet and --no-interaction too.

bin/cake some_command --no-interaction
# before: Error: Unknown option `no-interaction`.
# after:  prompts answer with their default, normal output stays visible

Not covered: options declared with 'prompt' => ... are asked while argv is parsed, before any flag is applied, so neither --quiet nor --no-interaction suppresses them. That is how it works today and would need argv pre-scanning; I left it out.

Open question for review: should core also get a --yes / ConsoleIo::confirm() for "assume yes" confirmations? cakephp/migrations#1128 adds a command-level --yes for now.

Docs: cakephp/docs follow-up once the API is agreed.

--quiet both lowers the output level and disables prompts. There was no
way to run a command non-interactively with normal output, and no getter
for the interactive state, so commands checked the output level instead.

--no-interaction is a long-only default option (-n is used by plugins)
that disables prompts without changing the output level. The interactive
state is now set before initialize(), so prompts there respect it too.
@dereuromark
dereuromark marked this pull request as ready for review November 20, 2026 17:42

$this->setOutputLevel($args, $io);
if ($args->getOption('quiet') || $args->getOption('no-interaction')) {
$io->setInteractive(false);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🤖 --no-interaction is applied after ConsoleOptionParser::parse() has already asked any questions defined with prompt, so commands can still wait for input and hang in automation. Could we apply it inside the parser, after reading the arguments but before prompting, and report missing required input as an error? That should avoid needing a separate argv pre-scan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants