Conditions | 11 |
Paths | 9 |
Total Lines | 9 |
Code Lines | 8 |
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 |
||
42 | private function processFilter($mode, $expected, $actual) { |
||
43 | if (Maphper::FIND_NOT & $mode) return $expected != $actual; |
||
44 | else if (Maphper::FIND_GREATER & $mode && Maphper::FIND_EXACT & $mode) return $expected <= $actual; |
||
45 | else if (Maphper::FIND_LESS & $mode && Maphper::FIND_EXACT & $mode) return $expected >= $actual; |
||
46 | else if (Maphper::FIND_GREATER & $mode) return $expected < $actual; |
||
47 | else if (Maphper::FIND_LESS & $mode) return $expected > $actual; |
||
48 | else if (Maphper::FIND_BETWEEN & $mode) return $expected[0] <= $actual && $actual <= $expected[1]; |
||
49 | else if (Maphper::FIND_NOCASE & $mode) return strtolower($expected) == strtolower($actual); |
||
50 | return $expected == $actual; |
||
51 | } |
||
53 |