Issues (11)

.phpstorm.meta.php/Group.php (3 issues)

1
<?php
2
3
namespace PHPSTORM_META {
4
5
    expectedArguments(\Yiisoft\Router\Group::getData(), 0, argumentsSet('groupDataKeys'));
0 ignored issues
show
Bug Best Practice introduced by
The method Yiisoft\Router\Group::getData() is not static, but was called statically. ( Ignorable by Annotation )

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

5
    expectedArguments(\Yiisoft\Router\Group::/** @scrutinizer ignore-call */ getData(), 0, argumentsSet('groupDataKeys'));
Loading history...
The call to Yiisoft\Router\Group::getData() has too few arguments starting with key. ( Ignorable by Annotation )

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

5
    expectedArguments(\Yiisoft\Router\Group::/** @scrutinizer ignore-call */ getData(), 0, argumentsSet('groupDataKeys'));

This check compares calls to functions or methods with their respective definitions. If the call has less 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...
6
7
    registerArgumentsSet(
8
        'groupDataKeys',
9
        'prefix',
10
        'namePrefix',
0 ignored issues
show
The call to PHPSTORM_META\registerArgumentsSet() has too many arguments starting with 'namePrefix'. ( Ignorable by Annotation )

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

10
    /** @scrutinizer ignore-call */ 
11
    registerArgumentsSet(

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...
11
        'host',
12
        'hosts',
13
        'corsMiddleware',
14
        'routes',
15
        'hasCorsMiddleware',
16
        'enabledMiddlewares',
17
    );
18
}
19