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

Improve wording when --skip-enable-extension #172

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ruudk
Copy link

@ruudk ruudk commented Jan 7, 2025

When --skip-enable-extension is used, it's done on purpose.

No need to uppercase not.
Explain how the extension can be enabled.

When `--skip-enable-extension` is used, it's done on purpose.

No need to uppercase not.
Explain how the extension can be enabled.
@@ -42,9 +42,9 @@ public function __invoke(
$output->writeln('Automatic extension enabling was skipped.', OutputInterface::VERBOSITY_VERBOSE);
}

$output->writeln('<comment>⚠️ Extension has NOT been automatically enabled.</comment>');
$output->writeln('<comment>⚠️ Extension is not enabled.</comment>');
Copy link
Collaborator

Choose a reason for hiding this comment

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

This messaging is not only emitted when --skip-enable-extension is used; it is also when we failed to automatically enable the extension. The messaging on the line above (Automatic extension enabling was skipped.) provides the context, although only with verbose mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants