| Conditions | 1 |
| Paths | 1 |
| Total Lines | 10 |
| Code Lines | 7 |
| Lines | 0 |
| Ratio | 0 % |
| Tests | 0 |
| CRAP Score | 2 |
| Changes | 0 | ||
| 1 | <?php |
||
| 28 | public function __construct(PromiseInterface $clientPromise, MessageProcessor $messageProcessor) |
||
| 29 | {
|
||
| 30 | parent::__construct($messageProcessor, new ClientHandShake()); |
||
| 31 | $clientPromise->then(function (Stream $stream) {
|
||
| 32 | $this->stream = $stream; |
||
| 33 | $this->onConnection($stream); |
||
| 34 | }, function (\Exception $error){
|
||
| 35 | $this->onError($error); |
||
|
|
|||
| 36 | }); |
||
| 37 | } |
||
| 38 | |||
| 64 |
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: