toplan /
phpsms
| Conditions | 14 |
| Paths | 16 |
| Total Lines | 24 |
| Code Lines | 16 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 2 | ||
| Bugs | 1 | Features | 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:
Methods with many parameters are not only hard to understand, but their parameters also often become inconsistent when you need more, or different data.
There are several approaches to avoid long parameter lists:
| 1 | <?php |
||
| 21 | public static function operateArray(array &$arr, $key, $value = null, $getDefault = null, \Closure $setAction = null, $override = false, $whenOverride = null, $isSet = false) |
||
| 22 | { |
||
| 23 | if (!$isSet && ($key === null || is_string($key) || is_int($key)) && $value === null) { |
||
| 24 | return $key === null ? $arr : |
||
| 25 | (isset($arr[$key]) ? $arr[$key] : $getDefault); |
||
| 26 | } |
||
| 27 | if ($override) { |
||
| 28 | if (is_callable($whenOverride)) { |
||
| 29 | call_user_func_array($whenOverride, [$arr]); |
||
| 30 | } |
||
| 31 | $arr = []; |
||
| 32 | } |
||
| 33 | if (is_array($key) || is_object($key)) { |
||
| 34 | foreach ($key as $k => $v) { |
||
| 35 | self::operateArray($arr, $k, $v, $getDefault, $setAction, false, null, true); |
||
| 36 | } |
||
| 37 | } elseif (is_callable($setAction)) { |
||
| 38 | call_user_func_array($setAction, [$key, $value]); |
||
| 39 | } else { |
||
| 40 | $arr[$key] = $value; |
||
| 41 | } |
||
| 42 | |||
| 43 | return $arr; |
||
| 44 | } |
||
| 45 | |||
| 65 |
