cycle /
database
| Conditions | 11 |
| Paths | 21 |
| Total Lines | 13 |
| Code Lines | 7 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 1 | ||
| 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:
| 1 | <?php |
||
| 27 | public static function toJson(mixed $value, bool $encode = true, bool $validate = true): string |
||
| 28 | { |
||
| 29 | if (!$encode && $validate && \is_string($value) && !json_validate($value)) { |
||
| 30 | throw new DriverException('Invalid JSON value.'); |
||
| 31 | } |
||
| 32 | |||
| 33 | if ($encode && !$validate) { |
||
| 34 | $value = \json_encode($value, \JSON_UNESCAPED_UNICODE|\JSON_THROW_ON_ERROR); |
||
| 35 | } |
||
| 36 | |||
| 37 | return $encode && $validate && (!\is_string($value) || !json_validate($value)) |
||
| 38 | ? \json_encode($value, \JSON_UNESCAPED_UNICODE|\JSON_THROW_ON_ERROR) |
||
| 39 | : $value; |
||
| 40 | } |
||
| 42 |
