| Conditions | 10 |
| Paths | 36 |
| Total Lines | 20 |
| Code Lines | 13 |
| 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 |
||
| 36 | public function progress(bool $blank = false) { |
||
| 37 | if ($blank) $teams = $this->from->isPlayed() ? $this->from->sortTeams($this->filters) : $this->from->simulate($this->filters); |
||
| 38 | else $teams = $this->from->sortTeams($this->filters); |
||
| 39 | |||
| 40 | if (count($this->filters) === 0 || $this->len !== null || $this->start !== 0) $next = array_splice($teams, $this->start, ($this->len === null ? count($teams) : $this->len)); |
||
| 41 | else $next = $teams; |
||
| 42 | |||
| 43 | $i = 1; |
||
| 44 | |||
| 45 | foreach ($next as $team) { |
||
| 46 | if ($blank) { |
||
| 47 | $this->to->addTeam(new BlankTeam($this.' - '.$i, $team)); |
||
| 48 | $i++; |
||
| 49 | } |
||
| 50 | else $team->sumPoints += $this->from->progressPoints; |
||
| 51 | } |
||
| 52 | |||
| 53 | $this->from->addProgressed($next); |
||
| 54 | if (!$blank) $this->to->addTeam($next); |
||
| 55 | return $this; |
||
| 56 | } |
||
| 59 |