| 1 | <?php |
||
| 13 | class CustomCommandDependencyProvider extends AbstractProvider |
||
| 14 | { |
||
| 15 | const SHELL_FACADE = 'shell.facade'; |
||
| 16 | |||
| 17 | /** |
||
| 18 | * @param \Xervice\Core\Dependency\DependencyProviderInterface $container |
||
| 19 | */ |
||
| 20 | 1 | public function handleDependencies(DependencyProviderInterface $container) |
|
| 24 | |||
| 25 | /** |
||
| 26 | * @param \Xervice\Core\Dependency\DependencyProviderInterface $container |
||
| 27 | */ |
||
| 28 | 1 | private function addShellFacade(DependencyProviderInterface $container): void |
|
| 34 | } |
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: