| 1 | <?php |
||
| 19 | class EntityBrowserListBuilder extends EntityListBuilder { |
||
| 20 | |||
| 21 | /** |
||
| 22 | * {@inheritdoc} |
||
| 23 | * |
||
| 24 | * We override ::render() so that we can add our own content above the table. |
||
| 25 | * parent::render() is where EntityListBuilder creates the table using our |
||
| 26 | * buildHeader() and buildRow() implementations. |
||
| 27 | */ |
||
| 28 | public function render() { |
||
| 35 | |||
| 36 | /** |
||
| 37 | * {@inheritdoc} |
||
| 38 | * |
||
| 39 | * Building the header and content lines for the entity browser list. |
||
| 40 | * |
||
| 41 | * Calling the parent::buildHeader() adds a column for the possible actions |
||
| 42 | * and inserts the 'edit' and 'delete' links as defined for the entity type. |
||
| 43 | */ |
||
| 44 | public function buildHeader() { |
||
| 49 | |||
| 50 | /** |
||
| 51 | * {@inheritdoc} |
||
| 52 | */ |
||
| 53 | public function buildRow(EntityInterface $entity) { |
||
| 59 | |||
| 60 | } |
||
| 61 |
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.