| Conditions | 1 |
| Paths | 1 |
| Total Lines | 13 |
| Lines | 0 |
| Ratio | 0 % |
| Tests | 7 |
| CRAP Score | 1 |
| Changes | 0 | ||
| 1 | <?php |
||
| 31 | private function registerRoleHierarchyResolver(Container $container) |
||
| 32 | { |
||
| 33 | 1 | $container['security.authorization.rolehierarchy'] = function () use ($container) { |
|
| 34 | 1 | return []; |
|
| 35 | }; |
||
| 36 | |||
| 37 | 1 | $container['security.authorization.rolehierarchyresolver'] = function () use ($container) { |
|
| 38 | 1 | return new RoleHierarchyResolver( |
|
| 39 | 1 | $container['security.authorization.rolehierarchy'], |
|
| 40 | 1 | $container['logger'] ?? null |
|
| 41 | ); |
||
| 42 | }; |
||
| 43 | 1 | } |
|
| 44 | } |
||
| 45 |
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: