The class Symfony\Bundle\Framework...d\ContainerAwareCommand has been deprecated with message: since Symfony 4.2, use {@see Command} instead.
This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.
The explanatory message should give you some clue as to whether and when the type will be
removed from the class and what other constant to use instead.
Loading history...
22
{
23
/**
24
* {@inheritdoc}
25
*/
26
public function configure(): void
27
{
28
$this->setName('sonata:notification:cleanup');
29
$this->setDescription('Clean up backend message');
30
}
31
32
/**
33
* {@inheritdoc}
34
*/
35
public function execute(InputInterface $input, OutputInterface $output): void
The return type of return $backend->getBackend(null); (Sonata\NotificationBundle\Backend\BackendInterface) is incompatible with the return type documented by Sonata\NotificationBundl...anupCommand::getBackend of type Sonata\NotificationBundl...d\BackendInterface|null.
If you return a value from a function or method, it should be a sub-type of the
type that is given by the parent type f.e. an interface, or abstract method.
This is more formally defined by the
Lizkov substitution principle,
and guarantees that classes that depend on the parent type can use any instance
of a child type interchangably. This principle also belongs to the
SOLID principles
for object oriented design.
Our function my_function expects a Post object, and outputs the author
of the post. The base class Post returns a simple string and outputting a
simple string will work just fine. However, the child class BlogPost which
is a sub-type of Post instead decided to return an object, and is
therefore violating the SOLID principles. If a BlogPost were passed to
my_function, PHP would not complain, but ultimately fail when executing the
strtoupper call in its body.
This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.
The explanatory message should give you some clue as to whether and when the type will be removed from the class and what other constant to use instead.