Conditions | 10 |
Paths | 7 |
Total Lines | 24 |
Code Lines | 12 |
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 |
||
22 | * @return DateTimeStandard|null |
||
23 | * |
||
24 | * @throws Exception if the value did not pass validation. |
||
25 | */ |
||
26 | public static function filter($value, bool $allowNull = false, DateTimeZone $timezone = null) |
||
27 | { |
||
28 | if ($value === null && $allowNull) { |
||
29 | return null; |
||
30 | } |
||
31 | |||
32 | if ($value instanceof \DateTime) { |
||
33 | return $value; |
||
34 | } |
||
35 | |||
36 | if (is_int($value) || ctype_digit($value)) { |
||
37 | $value = "@{$value}"; |
||
38 | } |
||
39 | |||
40 | if (!is_string($value) || trim($value) == '') { |
||
41 | throw new Exception('$value is not a non-empty string'); |
||
42 | } |
||
43 | |||
44 | return new \DateTime($value, $timezone); |
||
45 | } |
||
46 | |||
66 |
Let’s assume that you have a directory layout like this:
and let’s assume the following content of
Bar.php
:If both files
OtherDir/Foo.php
andSomeDir/Foo.php
are loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php
However, as
OtherDir/Foo.php
does not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php
, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: