zumba /
json-serializer
| 1 | <?php |
||
| 9 | class ClosureEntitySerializer implements EntitySerializer |
||
| 10 | { |
||
| 11 | /** |
||
| 12 | * @var ClosureSerializerInterface |
||
| 13 | */ |
||
| 14 | protected $closureSerializer; |
||
| 15 | |||
| 16 | /** |
||
| 17 | * ClosureEntitySerializer constructor. |
||
| 18 | * @param $closureSerializer |
||
| 19 | */ |
||
| 20 | public function __construct(ClosureSerializerInterface $closureSerializer) |
||
| 24 | |||
| 25 | /** |
||
| 26 | * @return string |
||
| 27 | */ |
||
| 28 | public function getType() |
||
| 32 | |||
| 33 | /** |
||
| 34 | * @param \Closure $object |
||
| 35 | * @return array |
||
| 36 | */ |
||
| 37 | public function serialize($object) |
||
| 44 | |||
| 45 | /** |
||
| 46 | * @param array $data |
||
| 47 | * @return \Closure |
||
| 48 | */ |
||
| 49 | public function unserialize($data) |
||
| 53 | |||
| 54 | } |
||
| 55 |
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: