Conditions | 1 |
Paths | 1 |
Total Lines | 12 |
Code Lines | 8 |
Lines | 0 |
Ratio | 0 % |
Changes | 0 |
1 | <?php |
||
13 | function qa_drush_command() { |
||
14 | $items['qa-dependencies'] = [ |
||
|
|||
15 | 'description' => 'Build a Graphviz DOT file showing the module and theme dependencies on the site', |
||
16 | 'aliases' => ['qadep'], |
||
17 | ]; |
||
18 | |||
19 | $items['qa-force-removed'] = [ |
||
20 | 'description' => 'List extensions removed without a clean uninstall.', |
||
21 | 'aliases' => ['qafrm'], |
||
22 | ]; |
||
23 | return $items; |
||
24 | } |
||
25 | |||
35 | } |
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
$myArray
is initialized the first time when the foreach loop is entered. You can also see that the value of thebar
key 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.