Building a single Command Application

When building a command line tool, you may not need to provide several commands.
In such case, having to pass the command name each time is tedious. Fortunately,
it is possible to remove this need by extending the application:

namespaceAcme\Tool;useSymfony\Component\Console\Application;useSymfony\Component\Console\Input\InputInterface;classMyApplicationextendsApplication{/** * Gets the name of the command based on input. * * @param InputInterface $input The input interface * * @return string The command name */protectedfunctiongetCommandName(InputInterface$input){// This should return the name of your command.return'my_command';}/** * Gets the default commands that should always be available. * * @return array An array of default Command instances */protectedfunctiongetDefaultCommands(){// Keep the core default commands to have the HelpCommand// which is used when using the --help option$defaultCommands=parent::getDefaultCommands();$defaultCommands[]=newMyCommand();return$defaultCommands;}/** * Overridden so that the application doesn't expect the command * name to be the first argument. */publicfunctiongetDefinition(){$inputDefinition=parent::getDefinition();// clear out the normal first argument, which is the command name$inputDefinition->setArguments();return$inputDefinition;}}

When calling your console script, the command MyCommand will then always
be used, without having to pass its name.