| Conditions | 2 |
| Paths | 2 |
| Total Lines | 14 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 19 | public function executeApiAction() |
||
| 20 | { |
||
| 21 | $this->getDatabase(); |
||
|
|
|||
| 22 | |||
| 23 | $userSearchHelper = UserSearchHelper::get($this->getDatabase()); |
||
| 24 | |||
| 25 | if (WebRequest::getString('all') === null) { |
||
| 26 | $userSearchHelper->byStatus(User::STATUS_ACTIVE); |
||
| 27 | |||
| 28 | } |
||
| 29 | |||
| 30 | $dataset = $userSearchHelper->fetchColumn('username'); |
||
| 31 | return $dataset; |
||
| 32 | } |
||
| 33 | } |
||
| 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: