1 | <?php |
||
11 | class ProductsController extends Controller |
||
12 | { |
||
13 | /** |
||
14 | * ProductsController constructor. |
||
15 | */ |
||
16 | public function __construct() |
||
21 | |||
22 | public function index() |
||
29 | |||
30 | public function categories() |
||
35 | |||
36 | /** |
||
37 | * [METHOD]: Add a new product in the database. |
||
38 | * |
||
39 | * @url:platform POST: /products/save |
||
40 | * @see:phpunit TODO: write phpunit test in a later version. |
||
41 | * |
||
42 | * @param Requests\ProductValidator $input |
||
43 | * @return \Illuminate\Http\RedirectResponse |
||
44 | */ |
||
45 | public function store(Requests\ProductValidator $input) |
||
61 | } |
||
62 |
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.