Completed
Push — master ( f172d4...76e139 )
by devosc
02:14
created

src/Config/ArrayAccess.php (8 issues)

Severity

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

1
<?php
2
/**
3
 *
4
 */
5
6
namespace Mvc5\Config;
7
8
trait ArrayAccess
9
{
10
    /**
11
     * @param string $name
12
     * @return mixed
13
     */
14
    abstract function get($name);
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
15
16
    /**
17
     * @param string $name
18
     * @return bool
19
     */
20
    abstract function has($name);
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
21
22
    /**
23
     * @param mixed $name
24
     * @return bool
25
     */
26 48
    function offsetExists($name)
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
27
    {
28 48
        return $this->has($name);
29
    }
30
31
    /**
32
     * @param mixed $name
33
     * @return mixed
34
     */
35 284
    function offsetGet($name)
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
36
    {
37 284
        return $this->get($name);
38
    }
39
40
    /**
41
     * @param mixed $name
42
     * @param mixed $value
43
     * @return mixed $value
44
     */
45 132
    function offsetSet($name, $value)
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
46
    {
47 132
        return $this->set($name, $value);
48
    }
49
50
    /**
51
     * @param mixed $name
52
     */
53 3
    function offsetUnset($name)
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
54
    {
55 3
        $this->remove($name);
56 3
    }
57
58
    /**
59
     * @param string $name
60
     * @return void
61
     */
62
    abstract function remove($name);
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
63
64
    /**
65
     * @param string $name
66
     * @param mixed $value
67
     * @return mixed
68
     */
69
    abstract function set($name, $value);
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
70
}
71