Conditions | 2 |
Paths | 2 |
Total Lines | 17 |
Code Lines | 7 |
Lines | 0 |
Ratio | 0 % |
Changes | 0 |
1 | <?php |
||
21 | public function run($console) |
||
22 | { |
||
23 | // parse the markdown file. |
||
24 | $this->call(ProcessMarkdownTemplatesTask::class); |
||
25 | |||
26 | // get docs types that needs to be generated by the user base on his configs. |
||
27 | $types = $this->call(GetDocsTypesTask::class); |
||
28 | |||
29 | $console->info("Generating API Documentations for (" . implode(' & ', $types) . ")\n"); |
||
30 | |||
31 | // for each type, generate docs. |
||
32 | foreach ($types as $type) { |
||
33 | $documentationUrls[] = $this->call(GenerateAPIDocsTask::class, [$type, $console]); |
||
|
|||
34 | } |
||
35 | |||
36 | $console->info("Done! You can access your API Docs at: \n" . implode("\n", $documentationUrls)); |
||
37 | } |
||
38 | |||
40 |
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.