| Conditions | 4 | 
| Paths | 1 | 
| Total Lines | 55 | 
| Lines | 0 | 
| Ratio | 0 % | 
| Changes | 0 | ||
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php | ||
| 70 | protected function _services() | ||
| 71 |     { | ||
| 72 | $this['config'] = Xhgui_Config::all(); | ||
| 73 | |||
| 74 |         $this['db'] = $this->share(function ($c) { | ||
| 75 | $config = $c['config']; | ||
| 76 |             if (empty($config['db.options'])) { | ||
| 77 | $config['db.options'] = array(); | ||
| 78 | } | ||
| 79 | $mongo = new MongoClient($config['db.host'], $config['db.options']); | ||
| 80 |             $mongo->{$config['db.db']}->results->findOne(); | ||
| 81 | |||
| 82 |             return $mongo->{$config['db.db']}; | ||
| 83 | }); | ||
| 84 | |||
| 85 |         $this['pdo'] = $this->share(function ($c) { | ||
| 86 | return new PDO( | ||
| 87 | $c['config']['pdo']['dsn'], | ||
| 88 | $c['config']['pdo']['pass'], | ||
| 89 | $c['config']['pdo']['user'] | ||
| 90 | ); | ||
| 91 | }); | ||
| 92 | |||
| 93 |         $this['searcher.mongo'] = function ($c) { | ||
| 94 | return new Xhgui_Searcher_Mongo($c['db']); | ||
| 95 | }; | ||
| 96 | |||
| 97 |         $this['searcher.pdo'] = function ($c) { | ||
| 98 | return new Xhgui_Searcher_Pdo($c['pdo'], $c['config']['pdo']['table']); | ||
| 99 | }; | ||
| 100 | |||
| 101 |         $this['searcher'] = function ($c) { | ||
| 102 | $config = $c['config']; | ||
| 103 | |||
| 104 |             switch ($config['save.handler']) { | ||
| 105 | case 'pdo': | ||
| 106 | return $c['searcher.pdo']; | ||
| 107 | |||
| 108 | case 'mongodb': | ||
| 109 | default: | ||
| 110 | return $c['searcher.mongo']; | ||
| 111 | } | ||
| 112 | }; | ||
| 113 | |||
| 114 |         $this['saver.mongo'] = function ($c) { | ||
| 115 | $config = $c['config']; | ||
| 116 | $config['save.handler'] = 'mongodb'; | ||
| 117 | |||
| 118 | return Xhgui_Saver::factory($config); | ||
| 119 | }; | ||
| 120 | |||
| 121 |         $this['saver'] = function ($c) { | ||
| 122 | return Xhgui_Saver::factory($c['config']); | ||
| 123 | }; | ||
| 124 | } | ||
| 125 | |||
| 153 | 
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: