How to Style a Console Command

Warning: You are browsing the documentation for Symfony 6.2, which is no longer maintained.

Read the updated version of this page for Symfony 7.1 (the current stable version).

How to Style a Console Command

One of the most boring tasks when creating console commands is to deal with the styling of the command's input and output. Displaying titles and tables or asking questions to the user involves a lot of repetitive code.

Consider for example the code used to display the title of the following command:

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
        // src/Command/GreetCommand.php
namespace App\Command;

use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;

class GreetCommand extends Command
{
    // ...

    protected function execute(InputInterface $input, OutputInterface $output): int
    {
        $output->writeln([
            '<info>Lorem Ipsum Dolor Sit Amet</>',
            '<info>==========================</>',
            '',
        ]);

        // ...
    }
}
    

Displaying a simple title requires three lines of code, to change the font color, underline the contents and leave an additional blank line after the title. Dealing with styles is required for well-designed commands, but it complicates their code unnecessarily.

In order to reduce that boilerplate code, Symfony commands can optionally use the Symfony Style Guide. These styles are implemented as a set of helper methods which allow to create semantic commands and forget about their styling.

Basic Usage

In your command, instantiate the SymfonyStyle class and pass the $input and $output variables as its arguments. Then, you can start using any of its helpers, such as title(), which displays the title of the command:

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
        // src/Command/GreetCommand.php
namespace App\Command;

use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;
use Symfony\Component\Console\Style\SymfonyStyle;

class GreetCommand extends Command
{
    // ...

    protected function execute(InputInterface $input, OutputInterface $output): int
    {
        $io = new SymfonyStyle($input, $output);
        $io->title('Lorem Ipsum Dolor Sit Amet');

        // ...
    }
}
    

Helper Methods

The SymfonyStyle class defines some helper methods that cover the most common interactions performed by console commands.

Titling Methods

title()

It displays the given string as the command title. This method is meant to be used only once in a given command, but nothing prevents you to use it repeatedly:

        1
        $io->title('Lorem ipsum dolor sit amet');
    

section()

It displays the given string as the title of some command section. This is only needed in complex commands which want to better separate their contents:

        1
2
3
4
5
6
7
        $io->section('Adding a User');

// ...

$io->section('Generating the Password');

// ...
    

Content Methods

text()

It displays the given string or array of strings as regular text. This is useful to render help messages and instructions for the user running the command:

        1
2
3
4
5
6
7
8
9
10
11
        // use simple strings for short messages
$io->text('Lorem ipsum dolor sit amet');

// ...

// consider using arrays when displaying long messages
$io->text([
    'Lorem ipsum dolor sit amet',
    'Consectetur adipiscing elit',
    'Aenean sit amet arcu vitae sem faucibus porta',
]);
    

listing()

It displays an unordered list of elements passed as an array:

        1
2
3
4
5
        $io->listing([
    'Element #1 Lorem ipsum dolor sit amet',
    'Element #2 Lorem ipsum dolor sit amet',
    'Element #3 Lorem ipsum dolor sit amet',
]);
    

table()

It displays the given array of headers and rows as a compact table:

        1
2
3
4
5
6
7
8
        $io->table(
    ['Header 1', 'Header 2'],
    [
        ['Cell 1-1', 'Cell 1-2'],
        ['Cell 2-1', 'Cell 2-2'],
        ['Cell 3-1', 'Cell 3-2'],
    ]
);
    

horizontalTable()

It displays the given array of headers and rows as a compact horizontal table:

        1
2
3
4
5
6
7
8
        $io->horizontalTable(
    ['Header 1', 'Header 2'],
    [
        ['Cell 1-1', 'Cell 1-2'],
        ['Cell 2-1', 'Cell 2-2'],
        ['Cell 3-1', 'Cell 3-2'],
    ]
);
    

definitionList()

It displays the given key => value pairs as a compact list of elements:

        1
2
3
4
5
6
7
8
9
        $io->definitionList(
    'This is a title',
    ['foo1' => 'bar1'],
    ['foo2' => 'bar2'],
    ['foo3' => 'bar3'],
    new TableSeparator(),
    'This is another title',
    ['foo4' => 'bar4']
);
    

createTable()

Creates an instance of Table styled according to the Symfony Style Guide, which allows you to use features such as dynamically appending rows.

newLine()

It displays a blank line in the command output. Although it may seem useful, most of the times you won't need it at all. The reason is that every helper already adds their own blank lines, so you don't have to care about the vertical spacing:

        1
2
3
4
5
        // outputs a single blank line
$io->newLine();

// outputs three consecutive blank lines
$io->newLine(3);
    

Admonition Methods

note()

It displays the given string or array of strings as a highlighted admonition. Use this helper sparingly to avoid cluttering command's output:

        1
2
3
4
5
6
7
8
9
10
11
        // use simple strings for short notes
$io->note('Lorem ipsum dolor sit amet');

// ...

// consider using arrays when displaying long notes
$io->note([
    'Lorem ipsum dolor sit amet',
    'Consectetur adipiscing elit',
    'Aenean sit amet arcu vitae sem faucibus porta',
]);
    

caution()

Similar to the note() helper, but the contents are more prominently highlighted. The resulting contents resemble an error message, so you should avoid using this helper unless strictly necessary:

        1
2
3
4
5
6
7
8
9
10
11
        // use simple strings for short caution message
$io->caution('Lorem ipsum dolor sit amet');

// ...

// consider using arrays when displaying long caution messages
$io->caution([
    'Lorem ipsum dolor sit amet',
    'Consectetur adipiscing elit',
    'Aenean sit amet arcu vitae sem faucibus porta',
]);
    

Progress Bar Methods

progressStart()

It displays a progress bar with a number of steps equal to the argument passed to the method (don't pass any value if the length of the progress bar is unknown):

        1
2
3
4
5
        // displays a progress bar of unknown length
$io->progressStart();

// displays a 100-step length progress bar
$io->progressStart(100);
    

progressAdvance()

It makes the progress bar advance the given number of steps (or 1 step if no argument is passed):

        1
2
3
4
5
        // advances the progress bar 1 step
$io->progressAdvance();

// advances the progress bar 10 steps
$io->progressAdvance(10);
    

progressFinish()

It finishes the progress bar (filling up all the remaining steps when its length is known):

        1
        $io->progressFinish();
    

progressIterate()

If your progress bar loops over an iterable collection, use the progressIterate() helper:

        1
2
3
4
5
        $iterable = [1, 2];

foreach ($io->progressIterate($iterable) as $value) {
    // ... do some work
}
    

createProgressBar()

Creates an instance of ProgressBar styled according to the Symfony Style Guide.

User Input Methods

ask()

It asks the user to provide some value:

        1
        $io->ask('What is your name?');
    

You can pass the default value as the second argument so the user can hit the <Enter> key to select that value:

        1
        $io->ask('Where are you from?', 'United States');
    

In case you need to validate the given value, pass a callback validator as the third argument:

        1
2
3
4
5
6
7
        $io->ask('Number of workers to start', '1', function (string $number): int {
    if (!is_numeric($number)) {
        throw new \RuntimeException('You must type a number.');
    }

    return (int) $number;
});
    

askHidden()

It's very similar to the ask() method but the user's input will be hidden and it cannot define a default value. Use it when asking for sensitive information:

        1
        $io->askHidden('What is your password?');
    

In case you need to validate the given value, pass a callback validator as the second argument:

        1
2
3
4
5
6
7
        $io->askHidden('What is your password?', function (string $password): string {
    if (empty($password)) {
        throw new \RuntimeException('Password cannot be empty.');
    }

    return $password;
});
    

confirm()

It asks a Yes/No question to the user and it only returns true or false:

        1
        $io->confirm('Restart the web server?');
    

You can pass the default value as the second argument so the user can hit the <Enter> key to select that value:

        1
        $io->confirm('Restart the web server?', true);
    

choice()

It asks a question whose answer is constrained to the given list of valid answers:

        1
        $io->choice('Select the queue to analyze', ['queue1', 'queue2', 'queue3']);
    

You can pass the default value as the third argument so the user can hit the <Enter> key to select that value:

        1
        $io->choice('Select the queue to analyze', ['queue1', 'queue2', 'queue3'], 'queue1');
    

Finally, you can allow users to select multiple choices. To do so, users must separate each choice with a comma (e.g. typing 1, 2 will select choice 1 and 2):

        1
        $io->choice('Select the queue to analyze', ['queue1', 'queue2', 'queue3'], multiSelect: true);
    

6.2

The multiSelect option of choice() was introduced in Symfony 6.2.

Result Methods

Note

If you print any URL it won't be broken/cut, it will be clickable - if the terminal provides it. If the "well formatted output" is more important, you can switch it off:

        1
        $io->getOutputWrapper()->setAllowCutUrls(true);
    

success()

It displays the given string or array of strings highlighted as a successful message (with a green background and the [OK] label). It's meant to be used once to display the final result of executing the given command, but you can use it repeatedly during the execution of the command:

        1
2
3
4
5
6
7
8
9
10
        // use simple strings for short success messages
$io->success('Lorem ipsum dolor sit amet');

// ...

// consider using arrays when displaying long success messages
$io->success([
    'Lorem ipsum dolor sit amet',
    'Consectetur adipiscing elit',
]);
    

info()

It's similar to the success() method (the given string or array of strings are displayed with a green background) but the [OK] label is not prefixed. It's meant to be used once to display the final result of executing the given command, without showing the result as a successful or failed one:

        1
2
3
4
5
6
7
8
9
10
        // use simple strings for short info messages
$io->info('Lorem ipsum dolor sit amet');

// ...

// consider using arrays when displaying long info messages
$io->info([
    'Lorem ipsum dolor sit amet',
    'Consectetur adipiscing elit',
]);
    

warning()

It displays the given string or array of strings highlighted as a warning message (with a red background and the [WARNING] label). It's meant to be used once to display the final result of executing the given command, but you can use it repeatedly during the execution of the command:

        1
2
3
4
5
6
7
8
9
10
        // use simple strings for short warning messages
$io->warning('Lorem ipsum dolor sit amet');

// ...

// consider using arrays when displaying long warning messages
$io->warning([
    'Lorem ipsum dolor sit amet',
    'Consectetur adipiscing elit',
]);
    

error()

It displays the given string or array of strings highlighted as an error message (with a red background and the [ERROR] label). It's meant to be used once to display the final result of executing the given command, but you can use it repeatedly during the execution of the command:

        1
2
3
4
5
6
7
8
9
10
        // use simple strings for short error messages
$io->error('Lorem ipsum dolor sit amet');

// ...

// consider using arrays when displaying long error messages
$io->error([
    'Lorem ipsum dolor sit amet',
    'Consectetur adipiscing elit',
]);
    

Configuring the Default Styles

By default, Symfony Styles wrap all contents to avoid having lines of text that are too long. The only exception is URLs, which are not wrapped, no matter how long they are. This is done to enable clickable URLs in terminals that support them.

If you prefer to wrap all contents, including URLs, use this method:

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
        // src/Command/GreetCommand.php
namespace App\Command;

// ...
use Symfony\Component\Console\Style\SymfonyStyle;

class GreetCommand extends Command
{
    // ...

    protected function execute(InputInterface $input, OutputInterface $output): int
    {
        $io = new SymfonyStyle($input, $output);
        $io->getOutputWrapper()->setAllowCutUrls(true);

        // ...
    }
}
    

6.2

The setAllowCutUrls() method was introduced in Symfony 6.2.

Defining your Own Styles

If you don't like the design of the commands that use the Symfony Style, you can define your own set of console styles. Create a class that implements the StyleInterface:

        1
2
3
4
5
6
7
8
        namespace App\Console;

use Symfony\Component\Console\Style\StyleInterface;

class CustomStyle implements StyleInterface
{
    // ...implement the methods of the interface
}
    

Then, instantiate this custom class instead of the default SymfonyStyle in your commands. Thanks to the StyleInterface you won't need to change the code of your commands to change their appearance:

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
        // src/Command/GreetCommand.php
namespace App\Console;

use App\Console\CustomStyle;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;

class GreetCommand extends Command
{
    // ...

    protected function execute(InputInterface $input, OutputInterface $output): int
    {
        // Before
        $io = new SymfonyStyle($input, $output);

        // After
        $io = new CustomStyle($input, $output);

        // ...
    }
}
    

Writing to the error output

If you reuse the output of a command as the input of other commands or dump it into a file for later reuse, you probably want to exclude progress bars, notes and other output that provides no real value.

Commands can output information in two different streams: stdout (standard output) is the stream where the real contents should be output and stderr (standard error) is the stream where the errors and the debugging messages should be output.

The SymfonyStyle class provides a convenient method called getErrorStyle() to switch between both streams. This method returns a new SymfonyStyle instance which makes use of the error output:

        1
2
3
4
5
6
7
        $io = new SymfonyStyle($input, $output);

// Write to the standard output
$io->write('Reusable information');

// Write to the error output
$io->getErrorStyle()->warning('Debugging information or errors');
    

Note

If you create a SymfonyStyle instance with an OutputInterface object that is not an instance of ConsoleOutputInterface, the getErrorStyle() method will have no effect and the returned object will still write to the standard output instead of the error output.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.

TOC

Version