signifly /
laravel-api-responder
| 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
|
|||
| 13 | } |
||
| 14 | } |
||
| 15 |
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.