SelfExecutionMiddleware::execute() - Code Metrics - spekkionu/tactician-container-selfhandling - Measure and Improve Code Quality continuously with Scrutinizer

SelfExecutionMiddleware::execute() A
last analyzed 2017-12-23 04:29 UTC

↳ Parent: SelfExecutionMiddleware

Complexity

Conditions	3
Paths	3

Size

Total Lines	10
Code Lines	6

Duplication

Lines	0
Ratio	0 %

Code Coverage

Tests	6
CRAP Score	3

Importance

Changes

Metric	Value
dl	0
loc	10
c	0
b	0
f	0
ccs	6
cts	6
cp	1
rs	9.4285
cc	3
eloc	6
nc	3
nop	2
crap	3

<?php
namespace Spekkionu\Tactician\SelfExecuting;

use League\Tactician\Middleware;

/**
 * Middleware are the plugins of Tactician. They receive each command that's
 * given to the CommandBus and can take any action they choose. Middleware can
 * continue the Command processing by passing the command they receive to the
 * $next callable, which is essentially the "next" Middleware in the chain.
 *
 * Depending on where they invoke the $next callable, Middleware can execute
 * their custom logic before or after the Command is handled. They can also
 * modify, log, or replace the command they receive. The sky's the limit.
 */
class SelfExecutionMiddleware implements Middleware
{
    /**
     * @param object $command
     * @param callable $next
     * @return mixed
     * @throws CommandHasNoHandleMethodException
     */
    public function execute($command, callable $next)
    {
        if (!$command instanceof SelfExecutingCommand) {
            return $next($command);
        }
        if (!method_exists($command, 'handle')) {
            throw new CommandHasNoHandleMethodException('Command does not have handle method');
        }
        return $command->handle();

    }
}


1		<?php
2		namespace Spekkionu\Tactician\SelfExecuting;
3
4		use League\Tactician\Middleware;
5
6		/**
7		* Middleware are the plugins of Tactician. They receive each command that's
8		* given to the CommandBus and can take any action they choose. Middleware can
9		* continue the Command processing by passing the command they receive to the
10		* $next callable, which is essentially the "next" Middleware in the chain.
11		*
12		* Depending on where they invoke the $next callable, Middleware can execute
13		* their custom logic before or after the Command is handled. They can also
14		* modify, log, or replace the command they receive. The sky's the limit.
15		*/
16		class SelfExecutionMiddleware implements Middleware
17		{
18		/**
19		* @param object $command
20		* @param callable $next
21		* @return mixed
22		* @throws CommandHasNoHandleMethodException
23		*/
24	3	public function execute($command, callable $next)
25		{
26	3	if (!$command instanceof SelfExecutingCommand) {
27	1	return $next($command);
28		}
29	2	if (!method_exists($command, 'handle')) {
30	1	throw new CommandHasNoHandleMethodException('Command does not have handle method');
31		}
32	1	return $command->handle();
		0 ignored issues – show Bug introduced 2016-10-26 00:32 UTC by Report Bug Copy Issue Report The method `handle()` does not seem to exist on `object<Spekkionu\Tactici...g\SelfExecutingCommand>`. This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
33		}
34		}
35

spekkionu / tactician-container-selfhandling

SelfExecutionMiddleware::execute() A last analyzed 2017-12-23 04:29 UTC

Complexity

Size

Duplication

Code Coverage

Importance

Duplication Side-by-Side

Filter issues like

SelfExecutionMiddleware::execute() A
last analyzed 2017-12-23 04:29 UTC