new Doyo\Bridge\CodeCoverage\Driver\Dummy() of type Doyo\Bridge\CodeCoverage\Driver\Dummy is incompatible with the type string expected by parameter $name of Symfony\Component\Depend...terface::getParameter().
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
22
$dummy = $container->getParameter(/** @scrutinizer ignore-type */ new Dummy());
The call to Doyo\Bridge\CodeCoverage\Processor::__construct() has too many arguments starting with $filter.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
24
$processor = /** @scrutinizer ignore-call */ new Processor($dummy, $filter);
This check compares calls to functions or methods with their respective definitions.
If the call has more arguments than are defined, it raises an issue.
If a function is defined several times with a different number of parameters, the
check may pick up the wrong definition and report false positives. One codebase
where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.
The method setProcessor() does not exist on Doyo\Bridge\CodeCoverage\Session\SessionInterface.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
25
$session->/** @scrutinizer ignore-call */
26
setProcessor($processor);
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.
The method setContainer() does not exist on Doyo\Bridge\CodeCoverage\Session\SessionInterface.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
26
$session->/** @scrutinizer ignore-call */
27
setContainer($container);
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.
doyolabs /
code-coverage
Loading history...