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

src/Config/PropertyAccess.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 PropertyAccess
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 string $name
24
     * @return void
25
     */
26
    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...
27
28
    /**
29
     * @param string $name
30
     * @param mixed $value
31
     * @return mixed
32
     */
33
    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...
34
35
    /**
36
     * @param mixed $name
37
     * @return mixed
38
     */
39 1
    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...
40
    {
41 1
        return $this->get($name);
42
    }
43
44
    /**
45
     * @param mixed $name
46
     * @return bool
47
     */
48 2
    function __isset($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...
49
    {
50 2
        return $this->has($name);
51
    }
52
53
    /**
54
     * @param mixed $name
55
     * @param mixed $value
56
     * @return mixed
57
     */
58 4
    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...
59
    {
60 4
        return $this->set($name, $value);
61
    }
62
63
    /**
64
     * @param mixed $name
65
     */
66 1
    function __unset($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...
67
    {
68 1
        $this->remove($name);
69 1
    }
70
}
71