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 call to Magento\Framework\DB\Select::order() has too many arguments starting with 'ASC'.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
29
)->/** @scrutinizer ignore-call */ order(
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...
30
)->limit(
31
$limit
32
);
33
34
$maxIdSelect = $connection->select()->from(
35
$subSetSelect,
36
['max_id'=>'MAX(entity_id)']
37
);
38
39
return $connection->fetchRow($maxIdSelect);
40
}
41
42
public function getUniqueTagsByMaxId(int $maxId):array
The call to Magento\Framework\DB\Select::from() has too many arguments starting with array('main_table' => self::TABLE_NAME).
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call 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.
integer-net /
magento2-async-varnish
Loading history...
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.