| Conditions | 1 |
| Paths | 1 |
| Total Lines | 10 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 18 | public function testNullTokenPersistence() |
||
| 19 | { |
||
| 20 | $tokenPersistence = new NullTokenPersistence(); |
||
| 21 | $token = new JwtToken('foo', new \DateTime('now')); |
||
| 22 | |||
| 23 | $tokenPersistence->saveToken($token); |
||
|
|
|||
| 24 | |||
| 25 | $this->assertFalse($tokenPersistence->hasToken()); |
||
| 26 | $this->assertNull($tokenPersistence->restoreToken()); |
||
| 27 | } |
||
| 28 | |||
| 44 |
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: