and let?s assume the following content of Bar.php:
// Bar.phpnamespaceOtherDir;useSomeDir\Foo;// This now conflicts the class OtherDir\Foo
If both files OtherDir/Foo.php and SomeDir/Foo.php are loaded in the
same runtime, you will see a PHP error such as the following:
PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php
However, as OtherDir/Foo.php does not necessarily have to be loaded and the
error is only triggered if it is loaded before OtherDir/Bar.php, this problem
might go unnoticed for a while. In order to prevent this error from surfacing,
you must import the namespace with a different alias:
// Bar.phpnamespaceOtherDir;useSomeDir\FooasSomeDirFoo;// There is no conflict anymore.
Loading history...
20
use Symfony\Component\Console\Input\InputInterface;
21
use Symfony\Component\Console\Output\OutputInterface;
22
use Symfony\Component\Finder\Finder;
23
24
/**
25
* Class ClearCacheCommand.
26
*/
27
class ClearCacheCommand extends Command implements CommandInterface
28
{
29
/**
30
* @var Config
31
*/
32
private $config;
33
34
/**
35
* @var LoggerInterface
36
*/
37
private $logger;
38
39
public function __construct(?string $name = null, Config $config, LoggerInterface $logger)
40
{
41
parent::__construct($name);
42
$this->config = $config;
43
$this->logger = $logger;
44
}
45
46
protected function configure(): void
47
{
48
$this
49
->setName('clear-cache')
50
->setAliases(array('cc'))
51
;
52
}
53
54
protected function execute(InputInterface $input, OutputInterface $output): void
Let?s assume that you have a directory layout like this:
and let?s assume the following content of
Bar.php
:If both files
OtherDir/Foo.php
andSomeDir/Foo.php
are loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php
However, as
OtherDir/Foo.php
does not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php
, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: