These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | declare(strict_types=1); |
||
4 | |||
5 | /* |
||
6 | * This file is part of the Sonata Project package. |
||
7 | * |
||
8 | * (c) Thomas Rabaix <[email protected]> |
||
9 | * |
||
10 | * For the full copyright and license information, please view the LICENSE |
||
11 | * file that was distributed with this source code. |
||
12 | */ |
||
13 | |||
14 | namespace Sonata\NotificationBundle\Event; |
||
15 | |||
16 | use Doctrine\Bundle\DoctrineBundle\Registry; |
||
17 | use Symfony\Bridge\Doctrine\RegistryInterface; |
||
18 | |||
19 | /** |
||
20 | * Doctrine context optimizer |
||
21 | * Used with doctrine backend to clear context taking care of the batch iterations. |
||
22 | * |
||
23 | * @author Kevin Nedelec <[email protected]> |
||
24 | */ |
||
25 | class DoctrineBackendOptimizeListener implements IterationListener |
||
26 | { |
||
27 | /** |
||
28 | * @var Registry |
||
29 | */ |
||
30 | protected $doctrine; |
||
31 | |||
32 | /** |
||
33 | * @param RegistryInterface $doctrine |
||
34 | */ |
||
35 | public function __construct(RegistryInterface $doctrine) |
||
36 | { |
||
37 | $this->doctrine = $doctrine; |
||
0 ignored issues
–
show
|
|||
38 | } |
||
39 | |||
40 | /** |
||
41 | * {@inheritdoc} |
||
42 | */ |
||
43 | public function iterate(IterateEvent $event): void |
||
44 | { |
||
45 | if (!method_exists($event->getIterator(), 'isBufferEmpty')) { |
||
46 | throw new \LogicException('You can\'t use DoctrineOptimizeListener with this iterator'); |
||
47 | } |
||
48 | |||
49 | if ($event->getIterator()->isBufferEmpty()) { |
||
0 ignored issues
–
show
It seems like you code against a concrete implementation and not the interface
Sonata\NotificationBundl...essageIteratorInterface as the method isBufferEmpty() does only exist in the following implementations of said interface: Sonata\NotificationBundl...rroneousMessageIterator , Sonata\NotificationBundl...eManagerMessageIterator , Sonata\NotificationBundl...eManagerMessageIterator .
Let’s take a look at an example: interface User
{
/** @return string */
public function getPassword();
}
class MyUser implements User
{
public function getPassword()
{
// return something
}
public function getDisplayName()
{
// return some name.
}
}
class AuthSystem
{
public function authenticate(User $user)
{
$this->logger->info(sprintf('Authenticating %s.', $user->getDisplayName()));
// do something.
}
}
In the above example, the authenticate() method works fine as long as you just pass instances of MyUser. However, if you now also want to pass a different implementation of User which does not have a getDisplayName() method, the code will break. Available Fixes
Note: PHP Analyzer uses reverse abstract interpretation to narrow down the types
inside the if block in such a case.
![]() |
|||
50 | $this->doctrine->getManager()->getUnitOfWork()->clear(); |
||
0 ignored issues
–
show
It seems like you code against a concrete implementation and not the interface
Doctrine\Common\Persistence\ObjectManager as the method getUnitOfWork() does only exist in the following implementations of said interface: Doctrine\ORM\Decorator\EntityManagerDecorator , Doctrine\ORM\EntityManager .
Let’s take a look at an example: interface User
{
/** @return string */
public function getPassword();
}
class MyUser implements User
{
public function getPassword()
{
// return something
}
public function getDisplayName()
{
// return some name.
}
}
class AuthSystem
{
public function authenticate(User $user)
{
$this->logger->info(sprintf('Authenticating %s.', $user->getDisplayName()));
// do something.
}
}
In the above example, the authenticate() method works fine as long as you just pass instances of MyUser. However, if you now also want to pass a different implementation of User which does not have a getDisplayName() method, the code will break. Available Fixes
Note: PHP Analyzer uses reverse abstract interpretation to narrow down the types
inside the if block in such a case.
![]() |
|||
51 | } |
||
52 | } |
||
53 | } |
||
54 |
Our type inference engine has found a suspicous assignment of a value to a property. This check raises an issue when a value that can be of a given class or a super-class is assigned to a property that is type hinted more strictly.
Either this assignment is in error or an instanceof check should be added for that assignment.