lagdo /
jaxon-dbadmin
| Conditions | 10 |
| Paths | 5 |
| Total Lines | 17 |
| Code Lines | 10 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 1 | ||
| Bugs | 0 | 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:
| 1 | <?php |
||
| 18 | private function getEditFunctionNames(TableFieldEntity $field, array $values, bool $update): array |
||
| 19 | { |
||
| 20 | $names = $values; |
||
| 21 | $dbFunctions = [$this->driver->insertFunctions(), $this->driver->editFunctions()]; |
||
| 22 | foreach ($dbFunctions as $key => $functions) { |
||
| 23 | if (!$key || (!isset($this->utils->input->values['call']) && $update)) { // relative functions |
||
| 24 | foreach ($functions as $pattern => $value) { |
||
| 25 | if (!$pattern || preg_match("~$pattern~", $field->type)) { |
||
| 26 | $names[] = $value; |
||
| 27 | } |
||
| 28 | } |
||
| 29 | } |
||
| 30 | if ($key && !preg_match('~set|blob|bytea|raw|file|bool~', $field->type)) { |
||
| 31 | $names[] = 'SQL'; |
||
| 32 | } |
||
| 33 | } |
||
| 34 | return $names; |
||
| 35 | } |
||
| 55 |
