| Conditions | 1 |
| Paths | 1 |
| Total Lines | 12 |
| Lines | 0 |
| Ratio | 0 % |
| Tests | 7 |
| CRAP Score | 1 |
| Changes | 0 | ||
| 1 | <?php |
||
| 15 | 1 | public function register(Container $container) |
|
| 16 | { |
||
| 17 | 1 | $this->registerRoleHierarchyResolver($container); |
|
|
|
|||
| 18 | |||
| 19 | 1 | $container['security.authorization.authorizations'] = function () use ($container) { |
|
| 20 | 1 | return []; |
|
| 21 | }; |
||
| 22 | |||
| 23 | 1 | $container['security.authorization'] = function () use ($container) { |
|
| 24 | 1 | return new AuthorizationStack($container['security.authorization.authorizations']); |
|
| 25 | }; |
||
| 26 | 1 | } |
|
| 27 | |||
| 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: