zemit-cms /
core
| Conditions | 1 |
| Paths | 1 |
| Total Lines | 9 |
| Code Lines | 6 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 1 | ||
| Bugs | 0 | Features | 0 |
| 1 | <?php |
||
| 37 | public function addBlameableBehavior(): void |
||
| 38 | { |
||
| 39 | $config = $this->getDI()->get('config'); |
||
| 40 | assert($config instanceof ConfigInterface); |
||
| 41 | |||
| 42 | $this->addBehavior(new Behavior\Blameable([ |
||
| 43 | 'auditClass' => $config->getModelClass(Audit::class), |
||
| 44 | 'auditDetailClass' => $config->getModelClass(AuditDetail::class), |
||
| 45 | 'userClass' => $config->getModelClass(User::class), |
||
| 46 | ])); |
||
| 49 |
Let?s assume that you have a directory layout like this:
. |-- OtherDir | |-- Bar.php | `-- Foo.php `-- SomeDir `-- Foo.phpand let?s assume the following content of
Bar.php:If both files
OtherDir/Foo.phpandSomeDir/Foo.phpare 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.phpHowever, as
OtherDir/Foo.phpdoes 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: