Respondable::respond()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 3
Code Lines 1

Duplication

Lines 0
Ratio 0 %

Importance

Changes 2
Bugs 0 Features 0
Metric Value
cc 1
eloc 1
c 2
b 0
f 0
nc 1
nop 2
dl 0
loc 3
rs 10
1
<?php
2
3
namespace Signifly\Responder\Concerns;
4
5
use Illuminate\Contracts\Support\Responsable;
6
use Signifly\Responder\Contracts\Responder;
7
8
trait Respondable
9
{
10
    protected function respond($data, ?string $resourceClass = null): Responsable
11
    {
12
        return app(Responder::class)->respond($data, $resourceClass);
0 ignored issues
show
Unused Code introduced by
The call to Signifly\Responder\Contracts\Responder::respond() has too many arguments starting with $resourceClass. ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-call  annotation

12
        return app(Responder::class)->/** @scrutinizer ignore-call */ respond($data, $resourceClass);

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...
13
    }
14
}
15