app()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 3
Code Lines 1

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 1
Metric Value
eloc 1
c 1
b 0
f 1
dl 0
loc 3
rs 10
cc 1
nc 1
nop 2
1
<?php
2
3
if (!function_exists('app')) {
4
    /**
5
     * Get the available container instance.
6
     *
7
     * @param string $make
8
     * @param array $parameters
9
     * @return mixed
10
     */
11
    function app($make = null, $parameters = [])
12
    {
13
        return \Nip\Container\Utility\Container::get($make, $parameters);
0 ignored issues
show
Bug introduced by
It seems like $make can also be of type string; however, parameter $make of Nip\Container\Utility\Container::get() does only seem to accept null, maybe add an additional type check? ( Ignorable by Annotation )

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

13
        return \Nip\Container\Utility\Container::get(/** @scrutinizer ignore-type */ $make, $parameters);
Loading history...
Unused Code introduced by
The call to Nip\Container\Utility\Container::get() has too many arguments starting with $parameters. ( Ignorable by Annotation )

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

13
        return \Nip\Container\Utility\Container::/** @scrutinizer ignore-call */ get($make, $parameters);

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