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.
Loading history...
19
->with($imageRaw)
20
->andReturn($imageExptected)
21
->once()
22
->getMock();
23
$pathExpected = '/path/to/graphic';
24
$parser = m::mock(FieldParserInterface::class)
25
->shouldReceive('getGraphic')
26
->andReturn($pathExpected)
27
->once()
28
->getMock();
29
$graphicResolver = function ($path) use ($pathExpected, $imageRaw) {
$imageManager of type Mockery\MockInterface is incompatible with the type Intervention\Image\ImageManager expected by parameter $imageManager of Graze\CiffRenderer\Rende...StaticGraphic::render().
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
$parser of type Mockery\MockInterface is incompatible with the type Graze\CiffRenderer\Parse...er\FieldParserInterface expected by parameter $parser of Graze\CiffRenderer\Rende...StaticGraphic::render().
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
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.