Setono\MessageSchedulerBundle\Command\DispatchCommand

Complexity

Total Complexity

4

Size/Duplication

Total Lines	27
Duplicated Lines	0 %

Test Coverage

Coverage

58.33%

Importance

Changes	2
Bugs	0	Features	0

3 Methods

Rating	Name	Duplication	Size	Complexity
A	__construct()	0	5	1
A	execute()	0	9	2
A	configure()	0	3	1

<?php

declare(strict_types=1);

namespace Setono\MessageSchedulerBundle\Command;

use Psr\Log\LoggerAwareInterface;
use Setono\MessageSchedulerBundle\Dispatcher\DispatcherInterface;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Logger\ConsoleLogger;
use Symfony\Component\Console\Output\OutputInterface;

final class DispatchCommand extends Command
{
    protected static $defaultName = 'setono:message-scheduler:dispatch';

    private DispatcherInterface $dispatcher;

    public function __construct(DispatcherInterface $dispatcher)
    {
        parent::__construct();

        $this->dispatcher = $dispatcher;
    }

    protected function configure(): void
    {
        $this->setDescription('Will dispatch messages, that are eligible for dispatching');
    }

    protected function execute(InputInterface $input, OutputInterface $output): int
    {
        if ($this->dispatcher instanceof LoggerAwareInterface) {
            $this->dispatcher->setLogger(new ConsoleLogger($output));

The method setLogger() does not exist on Setono\MessageSchedulerBundle\Dispatcher\DispatcherInterface. Since it exists in all sub-types, consider adding an abstract or default implementation to Setono\MessageSchedulerBundle\Dispatcher\DispatcherInterface.

        }

        $this->dispatcher->dispatch();

        return 0;
    }
}