It seems like the GitHub access token used for retrieving details about this repository from
GitHub became invalid. This might prevent certain types of inspections from being run (in
particular,
everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
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...
6
7
class DateTimeEntitySerializer implements EntitySerializer
8
{
9
const FORMAT = \DateTime::ATOM;
10
11
/**
12
* @return string
13
*/
14
public function getType()
15
{
16
return \DateTime::class;
17
}
18
19
/**
20
* @param $object
21
* @return array
22
*/
23
public function serialize($object)
24
{
25
return [
26
'time' => $object->format(self::FORMAT),
27
'timezone' => $object->getTimezone()->getName()
28
];
29
}
30
31
/**
32
* @param array $data
33
* @return \DateTime
34
*/
35
public function unserialize($data)
36
{
37
return \DateTime::createFromFormat(self::FORMAT, $data['time'], new \DateTimeZone($data['timezone']));
The expression \DateTime::createFromFor...ne($data['timezone'])); of type DateTime|false adds false to the return on line 37 which is incompatible with the return type documented by Zumba\JsonSerializer\Ent...Serializer::unserialize of type DateTime. It seems like you forgot to handle an error condition.
zumba /
json-serializer
Loading history...
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: