1 | <?php |
||
13 | class EntityBrowserListBuilder extends EntityListBuilder { |
||
14 | |||
15 | /** |
||
16 | * {@inheritdoc} |
||
17 | * |
||
18 | * Building the header and content lines for the entity browser list. |
||
19 | * |
||
20 | * Calling the parent::buildHeader() adds a column for the possible actions |
||
21 | * and inserts the 'edit' and 'delete' links as defined for the entity type. |
||
22 | */ |
||
23 | public function buildHeader() { |
||
28 | |||
29 | /** |
||
30 | * {@inheritdoc} |
||
31 | */ |
||
32 | public function buildRow(EntityInterface $entity) { |
||
38 | |||
39 | /** |
||
40 | * {@inheritdoc} |
||
41 | */ |
||
42 | protected function getDefaultOperations(EntityInterface $entity) { |
||
54 | |||
55 | } |
||
56 |
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.