for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;
use Symfony\Component\Console\Style\SymfonyStyle;
/**
* Class OutputStyle.
*
* Shameless copy/paste from Taylor Otwell's Laravel
*/
class OutputStyle extends SymfonyStyle
You can fix this by adding a namespace to your class:
namespace YourVendor; class YourClass { }
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.
{
* The output instance.
* @var \Symfony\Component\Console\Output\OutputInterface
private $output;
* Create a new Console OutputStyle instance.
* @param \Symfony\Component\Console\Input\InputInterface $input
* @param \Symfony\Component\Console\Output\OutputInterface $output
* @return void
@return
Adding a @return annotation to a constructor is not recommended, since a constructor does not have a meaningful return value.
Please refer to the PHP core documentation on constructors.
public function __construct(InputInterface $input, OutputInterface $output)
$this->output = $output;
parent::__construct($input, $output);
}
* Returns whether verbosity is quiet (-q).
* @return bool
public function isQuiet()
return $this->output->isQuiet();
* Returns whether verbosity is verbose (-v).
public function isVerbose()
return $this->output->isVerbose();
* Returns whether verbosity is very verbose (-vv).
public function isVeryVerbose()
return $this->output->isVeryVerbose();
* Returns whether verbosity is debug (-vvv).
public function isDebug()
return $this->output->isDebug();
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.