Conditions | 1 |
Paths | 1 |
Total Lines | 9 |
Lines | 0 |
Ratio | 0 % |
Tests | 7 |
CRAP Score | 1 |
Changes | 0 |
1 | <?php |
||
16 | 4 | public function __invoke(ControllerContainer $container, $ann) |
|
17 | { |
||
18 | 4 | $ref = new \ReflectionClass($container->getClassName()); |
|
19 | 4 | $container->getClassName(); |
|
|
|||
20 | |||
21 | 4 | $container->setDescription($ann->description); |
|
22 | 4 | $container->setSummary($ann->summary); |
|
23 | 4 | $container->setFileName($ref->getFileName()); |
|
24 | } |
||
25 | } |
PHP Analyzer performs a side-effects analysis of your code. A side-effect is basically anything that might be visible after the scope of the method is left.
Let’s take a look at an example:
If we look at the
getEmail()
method, we can see that it has no side-effect. Whether you call this method or not, no future calls to other methods are affected by this. As such code as the following is useless:On the hand, if we look at the
setEmail()
, this method _has_ side-effects. In the following case, we could not remove the method call: