| Conditions | 10 |
| Paths | 257 |
| Total Lines | 25 |
| Code Lines | 20 |
| Lines | 0 |
| Ratio | 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 |
||
| 56 | private function json_data($killIDs) |
||
| 57 | {
|
||
| 58 | $dna = array(); |
||
| 59 | foreach($killIDs as $killID) |
||
| 60 | {
|
||
| 61 | $killdata = Kills::getKillDetails($killID); |
||
| 62 | $dna[] = array( |
||
| 63 | "killtime" => $killdata["info"]["dttm"], |
||
| 64 | "SolarSystemName" => $killdata["info"]["solarSystemName"], |
||
| 65 | "solarSystemID" => $killdata["info"]["solarSystemID"], |
||
| 66 | "regionID" => $killdata["info"]["regionID"], |
||
| 67 | "regionName" => $killdata["info"]["regionName"], |
||
| 68 | "victimCharacterID" => isset($killdata["victim"]["characterID"]) ? $killdata["victim"]["characterID"] : null, |
||
| 69 | "victimCharacterName" => isset($killdata["victim"]["characterName"]) ? $killdata["victim"]["characterName"] : null, |
||
| 70 | "victimCorporationID" => isset($killdata["victim"]["corporationID"]) ? $killdata["victim"]["corporationID"] : null, |
||
| 71 | "victimCorporationName" => isset($killdata["victim"]["corporationName"]) ? $killdata["victim"]["corporationName"] : null, |
||
| 72 | "victimAllianceID" => isset($killdata["victim"]["allianceID"]) ? $killdata["victim"]["allianceID"] : null, |
||
| 73 | "victimAllianceName" => isset($killdata["victim"]["allianceName"]) ? $killdata["victim"]["allianceName"] : null, |
||
| 74 | "victimFactionID" => isset($killdata["victim"]["factionID"]) ? $killdata["victim"]["factionID"] : null, |
||
| 75 | "victimFactionName" => isset($killdata["victim"]["factionName"]) ? $killdata["victim"]["factionName"] : null, |
||
| 76 | "dna" => Fitting::DNA($killdata["items"], $killdata["victim"]["shipTypeID"]) |
||
| 77 | ); |
||
| 78 | } |
||
| 79 | return $dna; |
||
| 80 | } |
||
| 81 | } |
||
| 82 |
Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code.
Let’s take a look at an example:
As you can see in this example, the array
$myArrayis initialized the first time when the foreach loop is entered. You can also see that the value of thebarkey is only written conditionally; thus, its value might result from a previous iteration.This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization $myArray = array() either outside or inside the foreach loop.